Pods are failing NoVolumeConflictZone error when using pvc using default storage class created using kubernetes.io/cinder plugin in OCP 3

Issue

• We created a pvc using default storage class created using kubernetes.io/cinder plugin. PVC is created and bound to the above storage class but pods are failing when using this pvc with NoVolumeConflictZone error
• Should the cinder volume that is being claimed by pod through pvc and the node where the pod is being scheduled should be in the same availability zone?