[ICN-354] Fix ICN node reboot issue for the containerized version Created: 06/May/20  Updated: 17/Dec/20  Resolved: 16/Dec/20

Status: Done
Project: Integrated Cloud Native NFV
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Le Yao Assignee: Le Yao
Resolution: Done Votes: 0
Labels: icn-kud-r3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: KuD R3 Release works
Sprint: ICN Sprint 20, ICN Sprint 21, ICN Sprint 22, ICN Sprint 23

 Description   

As Kural suggests, change it in containerized installation.
Issue:After the node which install criproxy reboot, the criproxy service failed to start up and caused the virtlet failed to run.



 Comments   
Comment by Le Yao [ 22/Jun/20 ]

Patch has been submited to https://gerrit.onap.org/r/c/multicloud/k8s/+/109394

Generated at Sat Feb 10 05:59:16 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.