Bug 1804107
| Summary: | StorageClassName:Null shows up in StorageCluster.yaml for OCP 4.3 + OCS 4.2.1 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Neha Berry <nberry> | |
| Component: | Console Storage Plugin | Assignee: | Afreen <afrahman> | |
| Status: | CLOSED ERRATA | QA Contact: | Raz Tamir <ratamir> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | unspecified | CC: | afrahman, anbehl, aos-bugs, assingh, ebenahar, jefbrown, madam, nthomas, ocs-bugs, ratamir, uchapaga | |
| Target Milestone: | --- | Keywords: | Regression | |
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: DOM rendering was getting uncontrolled and not handling the states in a correct manner for the storage class dropdown.
Consequence: On initial render, the state of dropdown is getting cleared and set to null
Fix: Controlled unnecessary updates on UI to set the state properly.
Result: Storage class in not null
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1812907 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:15:41 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1812448, 1812907 | |||
|
Comment 9
Michael Adam
2020-03-04 22:23:17 UTC
Michael, We are working on it the fix that is required in UI. The component is not behaving expectedly for the dropdown of storage class selection. Needs some more investigation. Since this is a patch in openshift, not sure what we can do here for 4.3 tracking. @Elad, what do you suggest: move it out? Or keep it here for verification if we get an OCP z-stream update with the fix in time for OCS 4.3 GA? The issue is caused due to the different (In reply to Michael Adam from comment #11) > Since this is a patch in openshift, not sure what we can do here for 4.3 > tracking. > > @Elad, what do you suggest: move it out? > Or keep it here for verification if we get an OCP z-stream update with the > fix in time for OCS 4.3 GA? Let us wait until we get an OCP z-stream update with the fix in. we will try push and get this in asap (In reply to afrahman from comment #12) > The issue is caused due to the different I just checked , this comment got added by mistake. Please ignore @afreen, Please provide the nightly build detail for OCP 4.5 and we can start the verification process Since this is an OCP bug, will it be ok to test with GA'd OCS 4.2.2 or do we need internal rc builds of 4.2/4.3 ? This build has the fix https://openshift-release.svc.ci.openshift.org/releasestream/4.5.0-0.nightly/release/4.5.0-0.nightly-2020-03-12-153508. Any build after this will also work. Yes it can be tested with any OCS version. This bug is visible on all OCP versions (sometimes it is not as its a technical glitch). Thanks I verified this bug on OCP stable-4.5 with OCS 4.2 Hence moving the bug to verified state. 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 |