Bug 1939086 - [IBM][ROKS] Deploy RGW pods only if IBM COS is not available on platform
Summary: [IBM][ROKS] Deploy RGW pods only if IBM COS is not available on platform
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Jose A. Rivera
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1926831
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-15 15:17 UTC by Mudit Agarwal
Modified: 2021-03-23 09:31 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1926831
Environment:
Last Closed: 2021-03-23 04:44:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ocs-operator pull 1088 0 None closed Disable CephObjectStore when the cloud provider is IBMCloud 2021-03-15 15:21:43 UTC

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


Note You need to log in before you can comment on or make changes to this bug.