Bug 2240767
| Summary: | "Create StorageClass" page is breaking for ceph-csi and ceph-rbd provisioners | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Sanjal Katiyar <skatiyar> |
| Component: | management-console | Assignee: | Sanjal Katiyar <skatiyar> |
| Status: | CLOSED ERRATA | QA Contact: | Vishakha Kathole <vkathole> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.14 | CC: | kbg, kramdoss, nthomas, odf-bz-bot, vkathole |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.13.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.13.5-1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, in the web console, the following issues occurred because of the refactoring of storage class related code on the OpenShift (console) side:
1. When ceph-csi or ceph-rbd provisioner was selected, the page displayed runtime type error.
2. The default parameters for RADOS block device (RBD) or container storage interface (CSI) based classes were not getting added to the created storage class.
3. Form validations were not working correctly.
With this fix, the issues related to the OpenShift console in the newly refactored code are fixed. Also, a few changes are made on the OpenShift Data Foundation (odf-console) side to make sure the new changes are aligned. As a result, the functionality works without any error.
|
Story Points: | --- |
| Clone Of: | 2239033 | Environment: | |
| Last Closed: | 2023-12-13 12:58:17 UTC | Type: | --- |
| 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: | 2239033 | ||
| Bug Blocks: | |||
|
Description
Sanjal Katiyar
2023-09-26 11:32:53 UTC
since bug was introduced and fixed both in OCP (console) 4.14, on ODF (odf-console) 4.13 side we only need to send a fix for the release-4.13-compatibility branch (because that's what runs with OCP 4.14). no need to send a fix to release-4.13 branch of ODF (odf-console), as that will run with OCP (console) 4.13 and we don't have this bug in that version. (In reply to Sanjal Katiyar from comment #5) > since bug was introduced and fixed both in OCP (console) 4.14, on ODF > (odf-console) 4.13 side we only need to send a fix for the > release-4.13-compatibility branch (because that's what runs with OCP 4.14). > > no need to send a fix to release-4.13 branch of ODF (odf-console), as that > will run with OCP (console) 4.13 and we don't have this bug in that version. proposing for 4.13.4, PR is already up... proposing for 4.13.5 now as content for 4.13.4 is already finalised... 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 Data Foundation 4.13.5 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/RHBA-2023:7775 |