Bug 1895325

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

Created attachment 1726539 [details]
clustercreation

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

When installing OCS, the External option is disabled when the installation is tried on OCP running on Openstack platform

See attached

Version of all relevant components (if applicable):
4.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes

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)?
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:
No

Steps to Reproduce:
Create Storage cluster from web console on Openstack platform


Actual results:


Expected results:


Additional info:

--- Additional comment from anbehl on 2020-11-04 12:43:04 UTC ---

@sahina can you provide us the result for `oc get infrastructure -o yaml` for openstack platform?

--- Additional comment from sdudhgao on 2020-11-04 13:27:38 UTC ---

@Ankush,

% oc get infrastructure -o yaml


apiVersion: v1
items:
- apiVersion: config.openshift.io/v1
  kind: Infrastructure
  metadata:
    creationTimestamp: "2020-11-02T08:59:58Z"
    generation: 1
    managedFields:
    - apiVersion: config.openshift.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:spec:
          .: {}
          f:cloudConfig:
            .: {}
            f:key: {}
            f:name: {}
          f:platformSpec:
            .: {}
            f:type: {}
        f:status:
          .: {}
          f:apiServerInternalURI: {}
          f:apiServerURL: {}
          f:etcdDiscoveryDomain: {}
          f:infrastructureName: {}
          f:platform: {}
          f:platformStatus:
            .: {}
            f:openstack:
              .: {}
              f:apiServerInternalIP: {}
              f:ingressIP: {}
              f:nodeDNSIP: {}
            f:type: {}
      manager: cluster-bootstrap
      operation: Update
      time: "2020-11-02T08:59:58Z"
    name: cluster
    resourceVersion: "491"
    selfLink: /apis/config.openshift.io/v1/infrastructures/cluster
    uid: 239303c8-a912-454c-9b13-ff764b2a5a0a
  spec:
    cloudConfig:
      key: config
      name: cloud-provider-config
    platformSpec:
      type: OpenStack
  status:
    apiServerInternalURI: https://api-int.ocs.mkarnik.com:6443
    apiServerURL: https://api.ocs.mkarnik.com:6443
    etcdDiscoveryDomain: ocs.mkarnik.com
    infrastructureName: ocs-zxtzq
    platform: OpenStack
    platformStatus:
      openstack:
        apiServerInternalIP: 172.21.0.5
        ingressIP: 172.21.0.7
        nodeDNSIP: 172.21.0.6
      type: OpenStack
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

--- Additional comment from nberry on 2020-11-05 12:16:24 UTC ---

@Sahina are we planning to support External mode for RHV too ?

if yes, then should we get that added too ?

--- Additional comment from ykaul on 2020-11-05 16:13:31 UTC ---

(In reply to Neha Berry from comment #3)
> @Sahina are we planning to support External mode for RHV too ?
> 
> if yes, then should we get that added too ?

Why not? If it's on-prem, bare-metal or virtualized, there could be an RHCS around.

--- Additional comment from nberry on 2020-11-06 09:18:00 UTC ---

Raising the severity as OCS on Openstack(to be TP soon) and RHV(already TP) might/can be made to use external mode too in upcoming OCS z-stream release.