Description of problem: Due to large number of Input fields need to change it to a single text input box. Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 1/1 Steps to Reproduce: 1. Installed Operators -> OCS -> Create Storage Cluster 2. Select `Independent Mode` Actual results: Shows Input Fields Expected results: Should show text fields Additional info:
Setup: Provider:AWS OCP Version:4.5.0-0.nightly-2020-05-24-072501 OCS Version:ocs-operator.v4.5.0-433.ci Test process: 1.Go to "Operators" -> "Installed Operators" -> OCS -> Storage Cluster -> "Create OCS Cluster Service" 2.Select "Independent - For external storage" Result: white screen(need to refresh the web page)
This issue is an OCS Operator issue as the validation JSON annotation coming from OCS is irregular JSON. PR has been raised for that.
This bug has been moved to OCS as the annotation comes from the OCS Operator which was malformed and was breaking the UI. https://github.com/openshift/ocs-operator/pull/519 Fix has been merged.
Setup: Provider:AWS OCP Version: 4.5.0-0.nightly-2020-05-30-025738 OCS Version: ocs-operator.v4.5.0-439.ci Test process: 1.Go to "Operators" -> "Installed Operators" -> OCS -> Storage Cluster -> "Create OCS Cluster Service" 2.Select "Independent - For external storage" Result: white screen(need to refresh the web page) *attached screen record
Created attachment 1693831 [details] Independent Mode (white screen)
Is anyone looking at this?
This issue has been fixed. The OCS Operator which was used to test this did not have the fix in it. Oded can we test this out again?
Missing devel-ack?
(In reply to Bipul Adhikari from comment #6) > This bug has been moved to OCS as the annotation comes from the OCS Operator > which was malformed and was breaking the UI. > https://github.com/openshift/ocs-operator/pull/519 > Fix has been merged. (1) We shouldn't move bugs from one component that has been fixed to another component if a second layer problem has been uncovered. Instead, we should create a new bug for the new problem. (2) We should not be moving BZ status to MODIFIED or ON_QA if the bug is not qa-ack'ed. Since QE was already testing this, and moving to FailedQA, I guess it's ok but we need the ACK for the book-keeping. (==> Raz?)
acked
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, 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:2409