[ICN-327] criproxy failed to start up after node reboot Created: 13/Apr/20 Updated: 17/Dec/20 Resolved: 06/May/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | 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 14, ICN Sprint 16, ICN Sprint 17 |
| Description |
|
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 [ 13/Apr/20 ] |
|
Patch submited: |
| Comment by Le Yao [ 13/Apr/20 ] |
|
The kud will install the criproxy defaultly under the directory /tmp. |