Bug 1969945
| Summary: | isMultiAZDeployment set to true because it is considering not available cinderAZs | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | rlobillo |
| Component: | Storage | Assignee: | ShiftStack Bugwatcher <shiftstack-bugwatcher> |
| Storage sub component: | OpenStack CSI Drivers | QA Contact: | Jon Uriarte <juriarte> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | emacchi, pprinett, stephenfin |
| Version: | 4.8 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 15:26:10 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: | |||
Removing the Triaged keyword because: * the target release value is missing * the QE automation assessment (flag qe_test_coverage) is missing I think you've misunderstood what was happening here. The 'multiaz-cloud.conf' key was always appended to the config map. However, it was not used unless multiple AZs were detected. You can see that code here [1][2]. As for listing the available availability zones, this is already the case (and has been since this functionality was added to 'openstack-cinder-csi-driver-operator'). You can see the code for this here [3]. Hopefully this clears things up. I'm going to close this as NOTABUG. If you think I've missed something, please feel free to reopen this. [1] https://github.com/openshift/openstack-cinder-csi-driver-operator/blob/86a6edc85004b597953ac851635c23e4dafe7745/pkg/operator/starter.go#L162-L167 [2] https://github.com/openshift/openstack-cinder-csi-driver-operator/blob/86a6edc85004b597953ac851635c23e4dafe7745/pkg/operator/starter.go#L187-L192 [3] https://github.com/openshift/openstack-cinder-csi-driver-operator/blob/86a6edc85004b597953ac851635c23e4dafe7745/pkg/operator/cloudinfo.go#L109-L111 |
Version: 4.8.0-0.nightly-2021-06-08-034312 and RHOS-16.1-RHEL-8-20210323.n.0 Description of problem: Installation on a project with below AZ configuration: (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --compute +-----------+-------------+ | Zone Name | Zone Status | +-----------+-------------+ | nova | available | +-----------+-------------+ (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --volume +-----------+---------------+ | Zone Name | Zone Status | +-----------+---------------+ | nova | available | | cinderAZ0 | not available | | cinderAZ1 | not available | +-----------+---------------+ is triggering the configuration on the openstack-cinder-config configmap of the multiaz-cloud.conf: $ oc get cm -n openshift-cluster-csi-drivers openstack-cinder-config -o yaml apiVersion: v1 data: cloud.conf: | [Global] use-clouds = true clouds-file = /etc/kubernetes/secret/clouds.yaml cloud = openstack multiaz-cloud.conf: | [Global] use-clouds = true clouds-file = /etc/kubernetes/secret/clouds.yaml cloud = openstack [BlockStorage] ignore-volume-az = yes kind: ConfigMap metadata: creationTimestamp: "2021-06-08T16:29:35Z" name: openstack-cinder-config namespace: openshift-cluster-csi-drivers resourceVersion: "6181" uid: f7ec7e30-7889-4536-8457-93ba39b101b6 As only there are one avaiable compute AZ and one available cinder AZ and both have the same name, so there is no need to set the ignore-volume-az to 'yes' on the configmap. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. as OSP admin, disable the cinder-volume services for the cinder AZs. For example: openstack volume service set --disable hostgroup@tripleo_iscsi1 cinder-volume 2. Check that the tenant observes the AZs as disabled. 3. Run IPI installation and check the content of the config map. Actual results: multiaz-cloud.conf is appended on the config map data. Expected results: multiaz-cloud.conf should not be appended on the config map data.