Description of problem (please be detailed as possible and provide log snippests): On OCS 4.6 we see in the Web console UI, the option to deploy OCS in "External" mode is disabled. Please enable this for IBM Cloud Version of all relevant components (if applicable): OCS 4.6 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? We cannot use OCS in external mode. Is there any workaround available to the best of your knowledge? We can use CLI ways currently to try it out Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Open web console 2.After OCS operator deploy, when creating storage cluster the external mode is disabled Actual results: External mode is disabled Expected results: External mode should be allowed Additional info:
Last time I had asked, the value is platform: IBMCloud Akash, can you provide the output of below for the ROKS platform. (And is it the same on Satellite as well?) oc get infrastructure cluster -o yaml
@akgunjal.com Akash, can you help verify this bug?
Verified console fix with 4.8.0-rc.3 Requires a fix on the ibm-roks-toolkit side: https://github.com/openshift/ibm-roks-toolkit/pull/217
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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-2021:2438
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days