Hi Onap Team Sorry to interrupt you in your busy schedule. We would be grateful if you could give some insight on this matter.
Best Regards, Santosh Thapa Magar -----Original Message----- From: Santosh Thapa Magar <[email protected]> Sent: Tuesday, August 25, 2020 10:10 AM To: '[email protected]' <[email protected]> Subject: [Frankfurt] OOF Pods in Stuck Init State Hi Onap Team, We are trying to install full ONAP for Frankfurt 6.0.1 Version. After ONAP was deployed using helm command, we executed the healthcheck command and found that among 47 critical test, 45 passed, 2 failed. The failed test were 1. Basic OOF-Homing Health Check 2. Basic OOF-SNIRO Health Check There were some pods still in Init x/y status. dev-oof-has-api-8669785ffc-24nds 1/1 Running 0 9h dev-oof-has-controller-67dc8cfcd8-5dq46 1/1 Running 0 9h dev-oof-has-data-845cc7bdb6-t2c7j 0/1 Init:2/4 54 9h dev-oof-has-onboard-gj9xc 0/1 Completed 0 9h dev-oof-has-reservation-6b49496fdb-fm7lh 0/1 Init:2/4 54 9h dev-oof-has-solver-65dd6bb757-6dj6h 0/1 Init:2/4 54 9h dev-pap-75cc864df4-hx4wq 1/1 Running 0 9h We checked the status of Init Container of each pods and found the job dev-oof-has-healthcheck has not succeeded yet. $ kubectl get jobs -n onap NAME COMPLETIONS DURATION AGE dev-oof-has-healthcheck 0/1 9h 9h We would be grateful if you could provide us some insight to fix this issue. Best Regards Santosh Thapa Magar -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22007): https://lists.onap.org/g/onap-discuss/message/22007 Mute This Topic: https://lists.onap.org/mt/76398452/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
