Bug 1939086

Summary: [IBM][ROKS] Deploy RGW pods only if IBM COS is not available on platform
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Mudit Agarwal <muagarwa>
Component: ocs-operatorAssignee: Jose A. Rivera <jarrpa>
Status: CLOSED NEXTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: high    
Version: 4.6CC: ebenahar, jarrpa, jthottan, madam, muagarwa, nkashyap, ocs-bugs, owasserm, ratamir, sabose, sostapov
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1926831 Environment:
Last Closed: 2021-03-23 04:44:06 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: 1926831    
Bug Blocks:    

Description Mudit Agarwal 2021-03-15 15:17:59 UTC
+++ This bug was initially created as a clone of Bug #1926831 +++

Description of problem (please be detailed as possible and provide log
snippests):
On IBM Cloud/ROKS, deploy RGW pods only if the platform (for instance, Satellite environment) does not have IBM COS available

Version of all relevant components (if applicable):
4.7

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No - needed to optimize resources consumed

--- Additional comment from RHEL Program Management on 2021-02-09 14:31:04 UTC ---

This bug having no release flag set previously, is now set with release flag 'ocs‑4.7.0' to '?', and so is being proposed to be fixed at the OCS 4.7.0 release. If this bug should be proposed for a different release, please manually change the proposed release flag.

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 Sahina Bose on 2021-02-09 14:50:42 UTC ---

@akgunjal.com @nkashyap.com FYI. Neeraj, will you be working on this?

--- Additional comment from Sahina Bose on 2021-02-15 16:05:01 UTC ---

Neeraj, Akash - please confirm if you can own the testing for this bug on your environments.

--- Additional comment from Neeraj K Kashyap on 2021-02-15 16:06:26 UTC ---

Hi Sahina @sabose 
We are working on this, going to raise the PR this week. Thanks

--- Additional comment from RHEL Program Management on 2021-02-17 13:21:41 UTC ---

This BZ is being approved for OCS 4.7.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'ocs‑4.7.0'

--- Additional comment from RHEL Program Management on 2021-02-17 13:21:41 UTC ---

Since this bug has been approved for OCS 4.7.0 release, through release flag 'ocs-4.7.0+', the Target Release is being set to 'OCS 4.7.0'

--- Additional comment from Sahina Bose on 2021-02-23 16:56:08 UTC ---

This is needed for IBM ROKS in OCS 4.7

--- Additional comment from Mudit Agarwal on 2021-02-23 16:57:54 UTC ---

Do we have an upstream PR?

--- Additional comment from Sahina Bose on 2021-02-23 17:05:53 UTC ---

(In reply to Mudit Agarwal from comment #8)
> Do we have an upstream PR?

Updated the PR link

Comment 2 Mudit Agarwal 2021-03-15 15:21:45 UTC
Created this clone as the fix for this is required for https://bugzilla.redhat.com/show_bug.cgi?id=1937837

Comment 5 Mudit Agarwal 2021-03-23 04:44:06 UTC
As the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1937837 is no longer dependent on this BZ, I am moving this out of 4.6