Bug 2271593

this is not a "high" severity issue, that dropdown is not needed for any "Create StorageSystem" related functions... not even in multi-cluster use cases... user is not supposed to use that dropdown...

reducing the severity, this bug probably has been there since we first introduced the "Create StorageSystem" wizard flow...

(In reply to Sanjal Katiyar from comment #3)
> this is not a "high" severity issue, that dropdown is not needed for any
> "Create StorageSystem" related functions... not even in multi-cluster use
> cases... user is not supposed to use that dropdown...
>

in case of multi cluster, UI will automatically create the cluster in openshift-storge-extended namespace (plz check the official docs for more details)...

small correction to the description:
 
> Does this issue impact your ability to continue to work with the product
> (please explain in detail what is the user impact)?

> NO

in short that "Project Bar" simply displays the operator install namespace...

I don't quite agree that this issue should be given "low" priority. 
Firstly, it will be encountered by every new user attempting to deploy a cluster using the management console. 
Secondly, this is a regression.

> small correction to the description:
 
>> Does this issue impact your ability to continue to work with the product
>> (please explain in detail what is the user impact)?

>> NO

If we cannot select project, or if it does not have effect on created StorageSystem than the bar with selecting Project should be removed, to not confuse user. Similarly to PV or StorageClass creation pages.

> in short that "Project Bar" simply displays the operator install namespace...

I believe this is not described, and this is not straightforward

> I don't quite agree that this issue should be given "low" priority

this issue is "low" severity IMHO because no one ever need to use it while the deployment (neither in older versions of ODF nor newer) and it certainly not impact StorageSystem creation in anyway... so it should not be proposed for "4.15.0" as "high" severity issue (like it originally was)... 


> Firstly, it will be encountered by every new user attempting to deploy a cluster using the management console. 
> Secondly, this is a regression

we never document in the StorageSystem deployment steps to use this dropdown, so it is not really impacting anyone... (please let me know if that is not the case: https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html/deploying_openshift_data_foundation_using_bare_metal_infrastructure/deploy-using-local-storage-devices-bm)


> If we cannot select project, or if it does not have effect on created StorageSystem than the bar with selecting Project should be removed, to not confuse user.

I agree with this point, and it does make sense ! but this was UX suggestion (cc Chandan Kumar) to keep this Project dropdown bar to have similar experience like other operator operand's "Create" pages.


> I believe this is not described, and this is not straightforward

if this is not described, we can do so (if really needed and make sense to do so) or even have a discussion with UX team and remove it as a RFE BZ... (also, this dropdown is added by OCP, not ODF)

> I don't quite agree that this issue should be given "low" priority. 

I never said low "priority", I mentioned it as low "severity"... we can make priority as "medium" if that helps :)


> Similarly to PV or StorageClass creation pages.

PV and StorageClass are cluster-wide resources.

With ODF 4.16.0-90.stable we have "Namespace: openshift-storage-extended" in the header. Cluster does not have this ns, will it be created? What namespace name will be for the next StorageSystem we want to install? 
Adding screenshot

(In reply to Daniel Osypenko from comment #14)
> With ODF 4.16.0-90.stable we have "Namespace: openshift-storage-extended" in
> the header. Cluster does not have this ns, will it be created? What
> namespace name will be for the next StorageSystem we want to install? 
> Adding screenshot

Hi,

For the very first StorageSystem/StorageCluster creation this header will show namespace as "openshift-storage" (ODF operator install namespace).

Now, from 4.15 onwards we support multiple StorageSystems (1 internal + 1 external) (refer: https://issues.redhat.com/browse/RHSTOR-4422). So, for the second "Ceph" based StorageSystem/StorageCluster header will show the namespace as "openshift-storage-extended" which is created by UI (if not already existing) (this should be well documented in 4.15 docs as well).

We do not support more than 2 "Ceph" clusters, so header in that case is irrelevant (irrespective of any value which it might/might-not be showing) as "Next" button will always be blocked and user won't be able to create any more clusters.

Finally, IBM FlashSystem StorageSystem, this will always be created in "openshift-storage" and header should reflect the same when this option is selected.

Based on the screenshot and validation on ODF 4.16.0-90 moved to Verified

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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix 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-2024:4591