Bug 1810022 - [BAREMETAL] ocs-storagecluster did not get deployed from UI
Summary: [BAREMETAL] ocs-storagecluster did not get deployed from UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: management-console
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.5.0
Assignee: Pratik Surve
QA Contact: Pratik Surve
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-04 12:27 UTC by Pratik Surve
Modified: 2020-09-23 09:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-15 10:16:04 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5016 0 None closed OCS installation changes for baremetal infra 2020-12-18 08:41:58 UTC
Red Hat Product Errata RHBA-2020:3754 0 None None None 2020-09-15 10:16:45 UTC

Comment 3 Nishanth Thomas 2020-03-05 12:37:33 UTC 
This feature is being worked on and targeted for 4.5
Moving out.
Comment 4 Raz Tamir 2020-03-06 22:16:52 UTC 
Hi Nishanth,
BM is intended to be a tech preview in ocs 4.3 and therefore this bug is a direct blocker.

I'm moving it back to 4.3 to ensure we won't loose track of it.
Comment 5 Yaniv Kaul 2020-03-09 11:31:16 UTC 
(In reply to Raz Tamir from comment #4)
> Hi Nishanth,
> BM is intended to be a tech preview in ocs 4.3 and therefore this bug is a
> direct blocker.

It was well understood that it's not going to be deployed via the UI.

> 
> I'm moving it back to 4.3 to ensure we won't loose track of it.

It's going to be worked as part of OCP 4.5 UI, so moving it to OCS 4.3 is incorrect.
Comment 6 Raz Tamir 2020-03-10 09:04:34 UTC 
Hi Yaniv,

QE must have been missed a few details about this feature - could you please share where it was stated that the deployment should happen from CLI.
In 4.2 it was mentioned that deployment from the CLI is not the approach for customers so what have changed in 4.3?
Comment 7 Yaniv Kaul 2020-03-10 11:08:02 UTC 
(In reply to Raz Tamir from comment #6)
> Hi Yaniv,
> 
> QE must have been missed a few details about this feature - could you please
> share where it was stated that the deployment should happen from CLI.
> In 4.2 it was mentioned that deployment from the CLI is not the approach for
> customers so what have changed in 4.3?

For tech-preview, since we cannot discover and allow proper selection of the disks, this was the approach all along. We need to see where communication broke.
Comment 8 Raz Tamir 2020-03-10 12:26:30 UTC 
Ok thank Yaniv,

Moving to 4.5 based on the above discussion
Comment 9 Neha Gupta 2020-04-20 07:37:10 UTC 
Changes
Comment 10 Neha Gupta 2020-04-20 07:39:43 UTC 
Changes got merged. PR for it https://github.com/openshift/console/pull/5016
Comment 11 Yaniv Kaul 2020-06-24 15:37:19 UTC 
Neha - devel-ack please.
Comment 17 errata-xmlrpc 2020-09-15 10:16:04 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 (Red Hat OpenShift Container Storage 4.5.0 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/RHBA-2020:3754
Note You need to log in before you can comment on or make changes to this bug.