-
Bug
-
Resolution: Done
-
Medium
-
Dublin Release
-
None
-
Orange Openlab dublin-daily CI chain
Openstack Rocky
Kubernetes (installed with Kubespray / 1 controller + 12 compute nodes)
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}ONAP dublin
Orange Openlab dublin-daily CI chain Openstack Rocky Kubernetes (installed with Kubespray / 1 controller + 12 compute nodes) Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"} ONAP dublin results: http://testresults.opnfv.org/onap/api/v1/results?pod_name=onap_dublin_daily_pod4-OPNFV-oom&case_name=onap-k8s
The OOF pods are not Running after a fresh installation in Dublin
Please note that there is no error in our Master daily and OOM Gating chains (based on master).
But this issue seems more or less reproducible, it occurred on 5 of the 7 last iterations of the daily chain.
5 of the 6 pods in non running state after a fresh installation are OOF pods
- onap-oof-oof-has-api-bcc4df484-h65xv
- onap-oof-oof-has-controller-7c7864649c-tgmp4
- onap-oof-oof-has-data-6bbbdf8fd7-nrqxr
- onap-oof-oof-has-reservation-658b9c4f4f-nhf2f
- onap-oof-oof-has-solver-5d59f56856-g9hnk
- onap-sdnc-sdnc-ueb-listener-5d6b894df7-td2tv
and OOF-Homing healthcheck is FAIL
it sounds that the init is never completed.
the pod describe and logs can be found in the attached logs
2019-07-04 02:03:35,473 - INFO - onap-oof-oof-has-onboard has not succeeded yet
Error from server (BadRequest): container "oof-has-solver-health-readiness" in pod "onap-oof-oof-has-solver-5d59f56856-g9hnk" is waiting to start: PodInitializing