-
Bug
-
Resolution: Done-Errata
-
Critical
-
odf-4.16
-
None
Created attachment 2051335 [details]
backingstore_details_page
Description of problem (please be detailed as possible and provide log
snippests):
BackingStore details shows incorrect provider when it's created with GoogleCloudStorage option.
CR's spec still reports it correctly, but BackingStore's details page reports it as "IBM COS" (please check the attached screenshot):
apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
name: noobaa-default-backing-store
namespace: openshift-storage
ownerReferences:
- apiVersion: noobaa.io/v1alpha1
blockOwnerDeletion: true
controller: true
kind: NooBaa
name: noobaa
uid: ba6292d1-b4f5-4c26-b525-d72f63d50cec
finalizers: - noobaa.io/finalizer
labels:
app: noobaa
spec:
googleCloudStorage:
secret:
name: noobaa-gcp-bucket-creds
namespace: openshift-storage
targetBucket: noobaabucketffy37
type: google-cloud-storage
Version of all relevant components (if applicable):
OCP 4.17
ODF 4.16
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Is there any workaround available to the best of your knowledge?
Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
Can this issue reproducible?
Yes
Can this issue reproduce from the UI?
Yes, UI only bug.
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. Go to "Data Foundation > Object Storage > BackingStore > Create"
2. Choose "Google Cloud Storage" as a provider.
3. Create.
Actual results:
On details page of this BackingStore, under "Provider details" section, it's reported as "IBM COS".
Expected results:
Should be reported as "Google Cloud Storage".
Additional info:
- links to
-
RHBA-2024:138027 Red Hat OpenShift Data Foundation 4.18 security, enhancement & bug fix update