velero: Default-volumes-to-restic Stuck

What steps did you take and what happened: [A clear and concise description of what the bug is, and what commands you ran.) I have installed velero with --use-restic and version was 1.4.2 ,I was able to create volume backups with opt-in approach by annotating pods.I was looking forward for 1.5.2 release so I can use opt-out methot.I have upgraded velero it works normally When I create normal backups but when I try --default-volumes-to-restic option during backup creation it stucked in “In Progress”, describe shows total items 765 but backed up items stuck in 35.Size of Data in volumes are just megabytes.

What did you expect to happen: I expected it to backup volumes

The output of the following commands will help us better understand what’s going on: (Pasting long output into a GitHub gist or other pastebin is fine.) #2966 describe shows this Name: full-volume21 Namespace: velero Labels: velero.io/storage-location=default Annotations: velero.io/source-cluster-k8s-gitversion: v1.16.3 velero.io/source-cluster-k8s-major-version: 1 velero.io/source-cluster-k8s-minor-version: 16 API Version: velero.io/v1 Kind: Backup Metadata: Creation Timestamp: 2020-09-23T11:55:00Z Generation: 10 Resource Version: 1311467 Self Link: /apis/velero.io/v1/namespaces/velero/backups/full-volume21 UID: 5a609312-3fff-4d68-91d4-0b82c302ccb2 Spec: Default Volumes To Restic: true Hooks: Included Namespaces: * Storage Location: default Ttl: 720h0m0s Status: Expiration: 2020-10-23T11:55:00Z Format Version: 1.1.0 Phase: InProgress Progress: Items Backed Up: 35 Total Items: 765 Start Timestamp: 2020-09-23T11:55:00Z Version: 1 Events: <none>

• kubectl logs deployment/velero -n velero
• velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
• velero backup logs <backupname>
• velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
• velero restore logs <restorename>

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

• Velero version (use velero version):
• Velero features (use velero client config get features):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project’s top voted issues listed here.
Use the “reaction smiley face” up to the right of this comment to vote.

• 👍 for “I would like to see this bug fixed as soon as possible”
• 👎 for “There are more important bugs to focus on right now”