Akraino JIRA https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 [ICN-327] criproxy failed to start up after node reboot https://jira.akraino.org/browse/ICN-327 Integrated Cloud Native NFV <p>After the node which install criproxy reboot, the criproxy service failed to start up and caused the virtlet failed to run.</p> ICN-327 criproxy failed to start up after node reboot Bug Medium Done Done Le Yao Le Yao Mon, 13 Apr 2020 08:35:31 +0000 Thu, 17 Dec 2020 00:53:51 +0000 Wed, 6 May 2020 04:36:32 +0000 0 1 <p>Patch submited:<br/> <a href="https://gerrit.onap.org/r/c/multicloud/k8s/+/105831" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.onap.org/r/c/multicloud/k8s/+/105831</a></p> <p>The kud will install the criproxy defaultly under the directory /tmp.<br/> And /tmp dirctory will refresh after system reboot.<br/> Then criproxy cannot detect its binary file and failed to start up.</p> Development Epic Link ICN-217 Rank 0|i003vg: Sprint ICN Sprint 14 ICN Sprint 16 ICN Sprint 17