Bug 1894519 - [OSP] External mode cluster creation disabled for Openstack and oVirt platform
Summary: [OSP] External mode cluster creation disabled for Openstack and oVirt platform
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Ankush Behl
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks: 1895325
TreeView+ depends on / blocked
 
Reported: 2020-11-04 12:21 UTC by Sahina Bose
Modified: 2021-02-24 15:30 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:30:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
clustercreation (44.94 KB, image/png)
2020-11-04 12:21 UTC, Sahina Bose
no flags Details
screenshots of the page (279.20 KB, application/zip)
2020-12-10 11:56 UTC, Neha Berry
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7136 0 None closed Bug 1894519: Enable external mode for OpenStack and oVirt platform 2021-02-03 05:24:33 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:30:33 UTC

Description Sahina Bose 2020-11-04 12:21:29 UTC
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:

Comment 1 Ankush Behl 2020-11-04 12:43:04 UTC
@sahina can you provide us the result for `oc get infrastructure -o yaml` for openstack platform?

Comment 2 Servesha 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: ""

Comment 3 Neha Berry 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 ?

Comment 4 Yaniv Kaul 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.

Comment 5 Neha Berry 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.

Comment 7 Martin Bukatovic 2020-11-12 15:30:03 UTC
Why is this ON QA without acks nor target release set?

Comment 13 Neha Berry 2020-12-10 11:56:43 UTC
Created attachment 1738163 [details]
screenshots of the page

The fix was verified on following platforms

1. Openstack
2. RHV(Ovirt)

Attached here is the screenshot of the page where the radio option for external Mode is enabled for above two platforms

OCP build version  for OSP:  openshift-install-mac-4.7.0-0.ci-2020-11-25-230530

OCP build for For RHV - 4.7.0-0.nightly-2020-12-04-013308

Hence moving the BZ to verified

Comment 19 errata-xmlrpc 2021-02-24 15:30:03 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633


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