-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
Casablanca Release
-
None
-
None
As part of a full cluster for SDNC and the LF OSN conference - see LOG-789 for the deployment config "out of the box"
no logs available in the init state
Env for this cluster is using the helm deploy plugin
The 2nd env in the comments is a single 256g server (110 pod limit pushed to 700) using helm install
Will update later today after the OSN conference with more reproducable details - lowering priority for now
ubuntu@ip-172-31-14-89:~$ kubectl get pods --all-namespaces | grep oof onap onap-oof-oof-65d475fc68-vh9rk 1/1 Running 0 3h onap onap-oof-oof-has-api-6fc68b765f-vcpv9 0/1 Init:0/3 20 3h onap onap-oof-oof-has-controller-6555646546-87l5g 0/1 Init:0/3 20 3h onap onap-oof-oof-has-data-54d88b5467-rgbpm 0/1 Init:0/4 19 3h onap onap-oof-oof-has-healthcheck-tk9xf 0/1 Init:0/1 21 3h onap onap-oof-oof-has-onboard-4ln2z 0/1 Init:0/2 20 3h onap onap-oof-oof-has-reservation-698b6d4fc5-n667h 0/1 Init:0/4 20 3h onap onap-oof-oof-has-solver-c5c644678-chwhz 0/1 Init:0/4 20 3h
- relates to
-
LOG-789 create AWS cluster for use by Tim of SDNC-482
-
- Closed
-