Bug 1850334
| Summary: | noobaa-default-backing-store-noobaa-pod stuck in Pending State due to PVC issue in OCS 4.5.0-460.ci build | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Pratik Surve <prsurve> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | CLOSED ERRATA | QA Contact: | Sidhant Agrawal <sagrawal> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.5 | CC: | ebenahar, etamir, hnallurv, madam, nbecker, nberry, ocs-bugs, sagrawal, shan, sostapov, tnielsen |
| Target Milestone: | --- | Keywords: | AutomationBackLog, Regression |
| Target Release: | OCS 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.5.0-463.ci | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-15 10:17:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 3
Sébastien Han
2020-06-24 08:36:11 UTC
The related bug and PV fallback would be related to the OCS operator, so updating the component... I'll defer to Nimrod to confirm on this issue where the PVC is generated incorrectly. fallback is not related to the ocs-op, but in any case, we identified an issue which can cause this. I'm moving back to noobaa for now. devel-ack is missing. Hi Nimrod, Do you know how to simulate this bug? RGW was not deployed, that might be the only way to simulate this From what I see here, in order to verify the fix, we need to try creation of PV pool over BM cluster, using the exact same CRs used by Noobaa upon fallback to PV pool for the case if RGW is not created automatically. @Nimrod - where can we find these CRs? Use the NooBaa CLI to create a pv pool. Setup: Bare Metal OCP Version:4.5.0-0.nightly-2020-08-03-123303 OCS Version:ocs-operator.v4.5.0-515.ci Test Process: 1.Create PV-POOL storage class is localblock: $ nb -n openshift-storage backingstore create pv-pool pv-noobaa-test2 --num-volumes 1 --pv-size-gb 50 --storage-class localblock ERRO[0603] ❌ BackingStore "pv-noobaa-test2" Phase is "Rejected": Failed connecting all pods in backingstore for more than 10 minutes Current failing: 1 from requested: 1 2.Create PV-POOL storage class is localblock $ nb -n openshift-storage backingstore create pv-pool pv-noobaa-test --num-volumes 1 --pv-size-gb 50 --storage-class ocs-storagecluster-ceph-rbd INFO[0117] ✅ BackingStore "pv-noobaa-test" Phase is Ready 3.Get Pods status: $ oc get pod -n openshift-storage NAME READY STATUS RESTARTS AGE pv-noobaa-test-noobaa-pod-4915f96b 1/1 Running 0 4h34m pv-noobaa-test2-noobaa-pod-74eb5e9b 0/1 Pending 0 84m 4.Get PVC status: $ oc get pvc -n openshift-storage NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE 27h pv-noobaa-test-noobaa-pvc-4915f96b Bound pvc-2df985f3-5c47-4c68-b49b-435f998f69f0 50Gi RWO ocs-storagecluster-ceph-rbd 4h39m pv-noobaa-test2-noobaa-pvc-74eb5e9b Pending localblock 88m *What is the next step? *What are steps to reproduce this bug? (In reply to Oded from comment #20) > Setup: > Bare Metal > OCP Version:4.5.0-0.nightly-2020-08-03-123303 > OCS Version:ocs-operator.v4.5.0-515.ci > > > Test Process: > > 1.Create PV-POOL storage class is localblock: > $ nb -n openshift-storage backingstore create pv-pool pv-noobaa-test2 > --num-volumes 1 --pv-size-gb 50 --storage-class localblock > ERRO[0603] ❌ BackingStore "pv-noobaa-test2" Phase is "Rejected": Failed > connecting all pods in backingstore for more than 10 minutes Current > failing: 1 from requested: 1 > > 2.Create PV-POOL storage class is rbd > $ nb -n openshift-storage backingstore create pv-pool pv-noobaa-test > --num-volumes 1 --pv-size-gb 50 --storage-class ocs-storagecluster-ceph-rbd > INFO[0117] ✅ BackingStore "pv-noobaa-test" Phase is Ready > > 3.Get Pods status: > $ oc get pod -n openshift-storage > NAME READY > STATUS RESTARTS AGE > pv-noobaa-test-noobaa-pod-4915f96b 1/1 > Running 0 4h34m > pv-noobaa-test2-noobaa-pod-74eb5e9b 0/1 > Pending 0 84m > > 4.Get PVC status: > $ oc get pvc -n openshift-storage > NAME STATUS VOLUME > CAPACITY ACCESS MODES STORAGECLASS AGE > 27h > pv-noobaa-test-noobaa-pvc-4915f96b Bound > pvc-2df985f3-5c47-4c68-b49b-435f998f69f0 50Gi RWO > ocs-storagecluster-ceph-rbd 4h39m > pv-noobaa-test2-noobaa-pvc-74eb5e9b Pending > localblock 88m > > *What is the next step? > *What are steps to reproduce this bug? @Pratik, can you please check? @Pratik, can you please check? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Container Storage 4.5.0 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3754 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |