Description of problem: Currently(4.4.0 and below) the labeling of the namespace is part of the installation instruction which users might miss to add during the namespace creation. Making labeling as part of the deployment window can help avoid this problem. UX issue severity level: 2-High (refer below mentioned doc for severity levels) This BZ is being filed based on the Usability study conducted on RHOCS during July 2020. A complete report on this Usability study can be found here: https://docs.google.com/presentation/d/1w65Rl2ZsTew-TIqgKUaZ9Y-1DmG1Z4Y59sYQjYC_mMM/edit#slide=id.g547716335e_0_260 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Labeling is now automated as well (see BZ 1857275 for details), but it's not selected by default.
Based on comment from Console team. Closing this one as NOTABUG. https://bugzilla.redhat.com/show_bug.cgi?id=1871771#c6
Reopening and fixing this by Removing the option to label from OLM creation flow and directly labelling the namespace during storage cluster creation.
*** Bug 1894158 has been marked as a duplicate of this bug. ***
Created attachment 1740340 [details] Install-operator-page Logs copied - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/bz-1866298/
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
This comment was flagged a spam, view the edit history to see the original text if required.