Bug 2242880

Summary:	[4.13 clone] Noobaa should fallback to a pv-pool default BS when CCO is not providing credentials
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Danny <dzaken>
Component:	Multi-Cloud Object Gateway	Assignee:	Nimrod Becker <nbecker>
Status:	CLOSED ERRATA	QA Contact:	Uday kurundwade <ukurundw>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	kramdoss, odf-bz-bot, sdymnik
Target Milestone:	---
Target Release:	ODF 4.13.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.13.5-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2242854	Environment:
Last Closed:	2023-12-13 12:58:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2242854
Bug Blocks:

Description Danny 2023-10-09 14:49:20 UTC

+++ This bug was initially created as a clone of Bug #2242854 +++

Description of problem (please be detailed as possible and provide log
snippets):

when the cloud credentials operator can't or fails to provide credentials (e.g.: the CCO is in manual mode), the creation of noobaa is stuck, waiting for the CCO to create the credentials secret


Version of all relevant components (if applicable):


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?
yes. creating the default BS manually


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?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. install ODF in manual mode
2.
3.


Actual results:
noobaa installation is stuck pending on the credentials secret

Expected results:
noobaa should fallback to a pv pool BS after a timeout.
A proper alert should be generated, notifying the user of the failure to create a default BS of the intended type, and the creation of a pv-pool BS


Additional info:

--- Additional comment from RHEL Program Management on 2023-10-09 14:55:52 IDT ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.14.0' to '?', and so is being proposed to be fixed at the ODF 4.14.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from RHEL Program Management on 2023-10-09 17:44:10 IDT ---

This BZ is being approved for ODF 4.14.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.14.0

--- Additional comment from RHEL Program Management on 2023-10-09 17:44:10 IDT ---

Since this bug has been approved for ODF 4.14.0 release, through release flag 'odf-4.14.0+', the Target Release is being set to 'ODF 4.14.0

Comment 12 errata-xmlrpc 2023-12-13 12:58:19 UTC

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 Data Foundation 4.13.5 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/RHBA-2023:7775