When setting cluster monitoring to use the standard-csi storage class for prometheus in an environment with three Nova AZs (az1, az2, az3) and one Cinder AZ (nova), the prometheus pods hang in Pending status as the CSI driver is failing to create the Cinder volume due to an incorrect AZ specification.

Tested on 4.10.20, 4.11.9, and 4.12.0-ec.5

In an environment with Nova AZs but not Cinder AZs (common for environments using Ceph without DCN), deploy an OCP cluster and then attempt to set the storage for prometheus to use the standard-csi storage class.

1. Deploy OpenShift with default shift-on-stack configurations
2. Observe that ignore-volume-az is set to yes by default
3. Modify the cluster-monitoring-config ConfigMap to set a prometheus volumeClaimTemplate that uses the standard-csi storage class
4. Observe that prometheus pods are stuck in Pending status
5. View events on the created PVC and observe Cinder API responses indicating an incorrect AZ provided in the volume creation call

Volume creation fails and pods are stuck in Pending status

Volume is created without an AZ specified to Cinder (the in-tree behavior) and the pods start normally

Tested on OSP 16.2.3