Bug 1941000 - cinder storageclass creates persistent volumes with wrong label failure-domain.beta.kubernetes.io/zone in multi availability zones architecture on OSP 16.
Summary: cinder storageclass creates persistent volumes with wrong label failure-domai...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Hemant Kumar
QA Contact: Wei Duan
Depends On:
Blocks: 1942141
TreeView+ depends on / blocked
Reported: 2021-03-19 17:58 UTC by Mohamed Tleilia
Modified: 2021-07-27 22:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1942141 (view as bug list)
Last Closed: 2021-07-27 22:54:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 634 0 None open Bug 1941000: get AZ of cinder volume from cinder and not from metadata 2021-03-23 18:18:03 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:54:57 UTC

Comment 51 Wei Duan 2021-05-07 07:07:51 UTC
I verified following scenarios without setting the region on 4.8.0-0.nightly-2021-05-06-210840, did not met the issue mention in https://bugzilla.redhat.com/show_bug.cgi?id=1941000#c46 again, and do some storage basic test and passed.   

* OpenStack where nodes and storage both have a single availability zone (AZ) (typically "nova"). 
* OpenStack where nodes and storage have both a single AZ, but name of the AZ for nodes ("nova") is different that name of the AZ for storage (say "ceph").

Comment 54 errata-xmlrpc 2021-07-27 22:54:36 UTC
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.8.2 bug fix and security 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.


Note You need to log in before you can comment on or make changes to this bug.