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

CSI Restore stuck in "Finalising" state when using azure File csi driver

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • OADP 1.4.4
    • None
    • Documentation
    • None
    • 3
    • False
    • Hide

      None

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

      Description of problem:

      CSI Restore getting stuck in "Finalizing" state, on using azurefile-csi storageclass

      Version-Release number of selected component (if applicable):

      OADP 1.4.2 / OCP 4.17

      How reproducible:

      ALways

      Steps to Reproduce:
      1. Install any stateful application using azurefile-csi Storage class
      2. Perform backup, then remove application.
      3. Perform Restore of the same backup

      Actual results:

      Restore stuck in Finalising state

      Expected results:

      Restore should succeed.

      Additional info:

      backupName: csi1
  excludedResources:
  - nodes
  - events
  - events.events.k8s.io
  - backups.velero.io
  - restores.velero.io
  - resticrepositories.velero.io
  - csinodes.storage.k8s.io
  - volumeattachments.storage.k8s.io
  - backuprepositories.velero.io
  itemOperationTimeout: 1h0m0s
status:
  phase: Finalizing
  progress:
    itemsRestored: 54
    totalItems: 54
  startTimestamp: "2025-01-16T10:30:04Z"
  warnings: 14

      PVC pending

$ oc get pvc,pod -n 8pvc
NAME                            STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    VOLUMEATTRIBUTESCLASS   AGE
persistentvolumeclaim/volume1   Pending                                      azurefile-csi   <unset>                 9m19s
persistentvolumeclaim/volume2   Pending                                      azurefile-csi   <unset>                 9m19s
persistentvolumeclaim/volume3   Pending                                      azurefile-csi   <unset>                 9m19s
persistentvolumeclaim/volume4   Pending                                      azurefile-csi   <unset>                 9m19s
persistentvolumeclaim/volume5   Pending                                      azurefile-csi   <unset>                 9m19s
persistentvolumeclaim/volume6   Pending                                      azurefile-csi   <unset>                 9m18s
persistentvolumeclaim/volume7   Pending                                      azurefile-csi   <unset>                 9m18s
persistentvolumeclaim/volume8   Pending                                      azurefile-csi   <unset>                 9m18s

NAME                                 READY   STATUS    RESTARTS   AGE
pod/app-with-8pvc-84b7d6c659-49znh   0/1     Pending   0          9m18s

      9m31s       Warning   ProvisioningFailed     persistentvolumeclaim/volume8         failed to provision volume with StorageClass "azurefile-csi": error getting handle for DataSource Type VolumeSnapshot by Name velero-volume8-dpr5d: snapshot velero-volume8-dpr5d not bound

      $ oc get volumesnapshot -n 8pvc -w
NAME                   READYTOUSE   SOURCEPVC   SOURCESNAPSHOTCONTENT        RESTORESIZE   SNAPSHOTCLASS       SNAPSHOTCONTENT              CREATIONTIME   AGE
velero-volume1-d5p2q   true                     velero-volume1-d5p2q-dpkr2                 csi-azurefile-vsc   velero-volume1-d5p2q-dpkr2   45s            45s
velero-volume2-5hmg8   true                     velero-volume2-5hmg8-f6x88                 csi-azurefile-vsc   velero-volume2-5hmg8-f6x88   45s            45s
velero-volume3-rbzfl   true                     velero-volume3-rbzfl-k5mjt                 csi-azurefile-vsc   velero-volume3-rbzfl-k5mjt   45s            45s
velero-volume4-89b6d   true                     velero-volume4-89b6d-49b8b                 csi-azurefile-vsc   velero-volume4-89b6d-49b8b   45s            45s
velero-volume5-fnp78   true                     velero-volume5-fnp78-h7hqj                 csi-azurefile-vsc   velero-volume5-fnp78-h7hqj   45s            45s
velero-volume6-4h88j   true                     velero-volume6-4h88j-nxwwl                 csi-azurefile-vsc   velero-volume6-4h88j-nxwwl   45s            45s
velero-volume7-n2pww   true                     velero-volume7-n2pww-6drzd                 csi-azurefile-vsc   velero-volume7-n2pww-6drzd   45s            45s
velero-volume8-dpr5d   true                     velero-volume8-dpr5d-fh5s4                 csi-azurefile-vsc   velero-volume8-dpr5d-fh5s4   45s            45s

      NOTE: Datamover Backup/Restore for azure file CSI driver works as expected.
      Only CSI restore has the above issue.

      azure file csi snapshot is techpreview for 4.17, 4.18.

      {"name":"file.csi.azure.com","vendor_version":"v1.30.3"}

            [OADP-5508] CSI Restore stuck in "Finalising" state when using azure File csi driver

            PRABHA Kylasamiyer Sundara Rajan added a comment - - edited

            Hi,
            The note is published in Create a Restore CR: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/backup_and_restore/oadp-application-backup-and-restore#oadp-review-backup-restore_restoring-applications

            PRABHA Kylasamiyer Sundara Rajan added a comment - - edited Hi, The note is published in Create a Restore CR: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/backup_and_restore/oadp-application-backup-and-restore#oadp-review-backup-restore_restoring-applications

            A Arnold added a comment -

            rhn-support-pkylasam - please can you close with a link to the published documentation?
            Thanks

            A Arnold added a comment - rhn-support-pkylasam - please can you close with a link to the published documentation? Thanks

            Aziza Karol added a comment -

            rhn-support-anarnold can this be marked as done?

            Aziza Karol added a comment - rhn-support-anarnold can this be marked as done?

            PRABHA Kylasamiyer Sundara Rajan added a comment -

            Thanks rhn-support-anarnold ! I have updated the PR with the note.

            PRABHA Kylasamiyer Sundara Rajan added a comment - Thanks rhn-support-anarnold ! I have updated the PR with the note.

            A Arnold added a comment -

            rhn-support-pkylasam - we will add a single line admonition saying something like

            ```

            Azure File cloning does not supports NFS protocol. It supports the azurefile-csi storage class, which uses SMB protocol.
            ```
            I think a  [NOTE] would be sufficient

            A Arnold added a comment - rhn-support-pkylasam - we will add a single line admonition saying something like ``` Azure File cloning does not supports NFS protocol. It supports the  azurefile-csi  storage class, which uses SMB protocol. ``` I think a   [NOTE] would be sufficient

            Wes Hayutin added a comment -

            Azure CSI clone and snapshot are tech-preview.  We could doc it in OADP but it may be redundant.  Open to other opinions, thank you for testing this but we can close this issue if others agree.  

             

            https://docs.openshift.com/container-platform/4.17/storage/container_storage_interface/persistent-storage-csi.html

             

            • Azure File cloning does not supports NFS protocol. It supports the azurefile-csi storage class, which uses SMB protocol.
            • Azure File cloning and snapshot are Technology Preview features:
                Azure File CSI cloning and snapshot is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
              For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

            Wes Hayutin added a comment - Azure CSI clone and snapshot are tech-preview.  We could doc it in OADP but it may be redundant.  Open to other opinions, thank you for testing this but we can close this issue if others agree.     https://docs.openshift.com/container-platform/4.17/storage/container_storage_interface/persistent-storage-csi.html   Azure File cloning does not supports NFS protocol. It supports the  azurefile-csi  storage class, which uses SMB protocol. Azure File cloning and snapshot are Technology Preview features:   Azure File CSI cloning and snapshot is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see  Technology Preview Features Support Scope .

              rhn-support-pkylasam PRABHA Kylasamiyer Sundara Rajan
              rhn-support-ssingla Sachin Singla
              Sachin Singla Sachin Singla
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: