Bug 1909978

Summary: ignore-volume-az = yes not working on standard storageClass
Product: OpenShift Container Platform Reporter: rlobillo
Component: InstallerAssignee: Mike Fedosin <mfedosin>
Installer sub component: OpenShift on OpenStack QA Contact: Wei Duan <wduan>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: medium CC: mfedosin, piqin, pprinett, wduan
Version: 4.7Keywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:47:55 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:

Description rlobillo 2020-12-22 08:39:39 UTC
Applying the known workaround to enable the ability to create a PV when Nova Zone name is different from Cinder Zone name (https://github.com/openshift/installer/blob/master/docs/user/openstack/known-issues.md#cinder-availability-zones), the pvc is still stuck. It is using the standard storageClass which is deployed during installation and set as the default one.

$ oc describe pvc/pvc2
Name:          pvc2
Namespace:     test
StorageClass:  standard
Status:        Pending
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/cinder
               volume.kubernetes.io/selected-node: ostest-2sfsp-worker-0-z9fxb
Finalizers:    [kubernetes.io/pvc-protection]
Access Modes:  
VolumeMode:    Filesystem
Used By:       app
  Type     Reason               Age                    From                         Message
  ----     ------               ----                   ----                         -------
  Normal   WaitForPodScheduled  7m50s (x363 over 13h)  persistentvolume-controller  waiting for pod app to be scheduled
  Warning  ProvisioningFailed   3m20s (x344 over 13h)  persistentvolume-controller  Failed to provision volume with StorageClass "standard": failed to create a 1 GB volume: Bad request with: [POST], error message: {"badRequest": {"code": 400, "message": "Availability zone 'AZ0' is invalid."}}

Object definitions: 
$ cat pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
  name: pvc1
  - ReadWriteOnce
      storage: 1Gi
  storageClassName: standard

$ cat pod_with_pvc.yaml 
piVersion: v1
kind: Pod
  name: app
  - image: nginx
    imagePullPolicy: IfNotPresent
    name: nginx
    - containerPort: 80
      protocol: TCP
      - mountPath: /var/lib/www/data
        name: mydata
  - name: mydata
      claimName: pvc1
      readOnly: false

$ oc get storageclass standard -o yaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
  name: standard
provisioner: kubernetes.io/cinder
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

To workaround above issue, it is required to create a new storageClass that has the availability parameter set to nova, as below:

$ more sc-test.yaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
  name: sc-test
provisioner: kubernetes.io/cinder
  availability: nova
reclaimPolicy: Delete
volumeBindingMode: Immediate

In my opinion, either documentation should be updated including this, SCO should not require the availability parameter definition or the standard storageClass should include this parameter by default.


$ openshift-install version
openshift-install 4.7.0-0.nightly-2020-12-14-165231
built from commit ec982ecf5bd847add0f3af82b04f32251972701c
release image registry.svc.ci.openshift.org/ocp/release@sha256:c1efa679e0fc39b3a

Platform: Openstack RHOS-16.1-RHEL-8-20201124.n.0. IPI installation with Kuryr enabled on hybrid setup.

Comment 8 Wei Duan 2021-02-05 02:34:26 UTC
Verified pass.

Comment 11 errata-xmlrpc 2021-02-24 15:47:55 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.7.0 security, bug fix, and enhancement 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.