No pods shown in openshift-storage ns via latest image

[nehasharma5]

1. Install noobaa via ocs
2. wget https://raw.githubusercontent.com/openshift/ocs-operator/master/deploy/deploy-with-olm.yaml
3. Apply this OLM
   oc apply -f deploy-with-olm.yaml

Observed: No pods shown in openshift-storage ns

Workaround:
When change image to quay.io/ocs-dev/ocs-registry:4.8.0 , it start working
[root@api.new.cp.fyre.ibm.com ~]# oc get pod
NAME READY STATUS RESTARTS AGE
noobaa-core-0 1/1 Running 0 4m16s
noobaa-db-pg-0 1/1 Running 0 4m17s
noobaa-default-backing-store-noobaa-pod-19419d10 1/1 Running 0 2m15s
noobaa-endpoint-dd858556b-bgvnf 1/1 Running 0 2m19s
noobaa-operator-5b4875779c-4b2bn 1/1 Running 0 9m23s
ocs-metrics-exporter-6b5dcbc8c-lzkmp 1/1 Running 0 9m23s
ocs-operator-54d6758bb8-mqcvl 1/1 Running 0 9m23s
rook-ceph-operator-785779d4f9-f5mgb 1/1 Running 0 9m23s
[root@api.new.cp.fyre.ibm.com ~]#

Logs:
ocs-logs.tar.gz

[nehasharma5]

For @bssrikanth ocs-operator goes in crash Loop state
[root@hpoocpci-inf ~]# oc get pod
NAME READY STATUS RESTARTS AGE
noobaa-core-0 1/1 Running 0 7m19s
noobaa-operator-5596cc869f-jj5hj 1/1 Running 0 15m
ocs-metrics-exporter-6b5dcbc8c-jwzxx 1/1 Running 0 15m
ocs-operator-59579b7bd5-tqbzj 0/1 CrashLoopBackOff 7 15m
rook-ceph-operator-785779d4f9-sg8bk 1/1 Running 0 15m

For logs please refer : Please refer noobaa/noobaa-core#6721

[rkomandu]

oc get pod ocs-operator-59579b7bd5-84cfw -n openshift-storage
NAME READY STATUS RESTARTS AGE
ocs-operator-59579b7bd5-84cfw 0/1 CrashLoopBackOff 29 131m

oc describe pod
Events:
Type Reason Age From Message

---

Normal Scheduled 132m default-scheduler Successfully assigned openshift-storage/ocs-operator-59579b7bd5-84cfw to worker1.rkomandu-hpo.cp.fyre.ibm.com
Normal AddedInterface 132m multus Add eth0 [10.254.19.192/22]
Normal Pulled 132m kubelet Successfully pulled image "quay.io/ocs-dev/ocs-operator:latest" in 1.13448066s
Normal Pulled 132m kubelet Successfully pulled image "quay.io/ocs-dev/ocs-operator:latest" in 1.019054959s
Normal Pulled 131m kubelet Successfully pulled image "quay.io/ocs-dev/ocs-operator:latest" in 1.073621296s
Normal Pulling 131m (x4 over 132m) kubelet Pulling image "quay.io/ocs-dev/ocs-operator:latest"
Normal Created 131m (x4 over 132m) kubelet Created container ocs-operator
Normal Started 131m (x4 over 132m) kubelet Started container ocs-operator
Normal Pulled 131m kubelet Successfully pulled image "quay.io/ocs-dev/ocs-operator:latest" in 1.051985278s
Warning Unhealthy 130m (x4 over 132m) kubelet Readiness probe failed: Get "http://10.254.19.192:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning BackOff 2m23s (x574 over 132m) kubelet Back-off restarting failed container

AY VERSION REPLACES PHASE
ocs-operator.v4.8.0 OpenShift Container Storage 4.8.0 Failed

deploy.yaml is taken from https://raw.githubusercontent.com/openshift/ocs-operator/master/deploy/deploy-with-olm.yaml

[bssrikanth]

Can anyone have a look into this? this is kind of blocking for us move forward with our development items.

[jarrpa]

GitHub issues are not a good format for getting help. Please open a BZ against OpenShift Container Storage, using the ocs-operator component.

[nimrod-becker]

@jarrpa This applied when using deploy_with_olm which is mainly u/s ...

[obnoxxx]

if it is a defect, it should be reopened...