-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
ToDo
-
-
Hello team:
[ Description ]:
While running StorageClass Conversion using MTC over a volume that was successfully restored with OADP, we encountered the following errors:
2m53s Normal Provisioning persistentvolumeclaim/xxxxxxx External provisioner is provisioning volume for claim "yyyyyyyyyyy/xxxxxxx" 2m53s Warning ProvisioningFailed persistentvolumeclaim/xxxxxxxx failed to provision volume with StorageClass "ocs-storagecluster-cephfs": claim Selector is not supported
Checking on the PVC definition that is being converted, we noticed that it comes with a selector label:
$ oc get pvc xxxxxxxxx -o yaml |yq '.spec.selector' { "matchLabels": { "velero.io/dynamic-pv-restore": "xxxxxxxxxxx" } }
According to the following KCS or Kubernetes documentation, dynamically provisioned PVC's even if they are restored, should not come with a selector:
- https://access.redhat.com/solutions/6987406
- https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
This ticket is a follow-up to analyze if this could be fixed from the MTC perspective, as per OADP engineering determined in https://issues.redhat.com/browse/OADP-6507
- is duplicated by
-
OADP-6507 Wrong selector label on PVC created by velero impacts other components as MTC
-
- Closed
-