Bug 1659976
Summary: | Default storage class shows false even it is true | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Radomir Ludva <rludva> |
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
Status: | CLOSED ERRATA | QA Contact: | shahan <hasha> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas, wsun |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the 3.11 admin console did not correctly display whether a storage class was the default storage class since it was checking an out-of-date annotation value. The admin console has been updated to use the `storageclass.kubernetes.io/is-default-class=true` annotation, and service classes are now properly marked as default when that value is set.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-20 14:11:02 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: |
Description
Radomir Ludva
2018-12-17 10:03:51 UTC
This is fixed in 4.0. Backporting the fix. https://github.com/openshift/console/pull/958 The previous 3.11 PR was replaced with https://github.com/openshift/console/pull/858 StorageClass default status is true when setting storageclass.kubernetes.io/is-default-class: "true" brewregistry.stage.redhat.io/openshift3/ose-console v3.11 21e477ce12d8 3 hours ago 254 MB openshift v3.11.82 verified this bug 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-2019:0326 |