Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-6507

Wrong selector label on PVC created by velero impacts other components as MTC

XMLWordPrintable

    • Incidents & Support
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None

      [ 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:

              wnstb Wes Hayutin
              rhn-support-lperezbe Luis Perez Besa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: