Bug 2258801
| Summary: | [Provider-Client] Noobaa backingstore is created on a PV pool instead of RGW | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Jilju Joy <jijoy> |
| Component: | ocs-operator | Assignee: | Leela Venkaiah Gangavarapu <lgangava> |
| Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.14 | CC: | ammahapa, lgangava, mparida, muagarwa, nberry, odf-bz-bot |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.16.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-07-17 13:12:01 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: | |||
|
Description
Jilju Joy
2024-01-17 12:42:36 UTC
Adding yaml output of backingstore noobaa-default-backing-store which is missing in bug Description.
$ oc get backingstore noobaa-default-backing-store -n openshift-storage -o yaml
apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
creationTimestamp: "2024-01-13T10:14:10Z"
finalizers:
- noobaa.io/finalizer
generation: 1
labels:
app: noobaa
name: noobaa-default-backing-store
namespace: openshift-storage
ownerReferences:
- apiVersion: noobaa.io/v1alpha1
blockOwnerDeletion: true
controller: true
kind: NooBaa
name: noobaa
uid: 4b48f1ab-6997-4833-886b-81fbecfb6f5f
resourceVersion: "6292643"
uid: eca8228f-1926-4a52-bba4-cc5c6c59b622
spec:
pvPool:
numVolumes: 1
resources:
requests:
storage: 50Gi
secret: {}
storageClass: ocs-storagecluster-ceph-rbd
type: pv-pool
status:
conditions:
- lastHeartbeatTime: "2024-01-17T12:56:55Z"
lastTransitionTime: "2024-01-17T12:56:55Z"
message: BackingStorePhaseReady
reason: 'Backing store mode: OPTIMAL'
status: "True"
type: Available
- lastHeartbeatTime: "2024-01-17T12:56:55Z"
lastTransitionTime: "2024-01-17T12:56:55Z"
message: BackingStorePhaseReady
reason: 'Backing store mode: OPTIMAL'
status: "False"
type: Progressing
- lastHeartbeatTime: "2024-01-17T12:56:55Z"
lastTransitionTime: "2024-01-17T09:49:15Z"
message: BackingStorePhaseReady
reason: 'Backing store mode: OPTIMAL'
status: "False"
type: Degraded
- lastHeartbeatTime: "2024-01-17T12:56:55Z"
lastTransitionTime: "2024-01-17T12:56:55Z"
message: BackingStorePhaseReady
reason: 'Backing store mode: OPTIMAL'
status: "True"
type: Upgradeable
mode:
modeCode: OPTIMAL
timeStamp: 2024-01-17 09:49:15.786131426 +0000 UTC m=+348024.816926495
phase: Ready
Moving the non-blocker BZ out, please bring it back with a blocker justification if required. 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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix 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/RHSA-2024:4591 |