Velero: failure of volumes --snapshot-volumes0

Created on 18 Jun 2019 · 9Comments · Source: vmware-tanzu/velero

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.)

What did you expect to happen:

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.)

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):
Kubernetes version (use kubectl version):
Kubernetes installer & version:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):

Question

Source

gkdba87

All 9 comments

We are trying to take backup of namespace in k8 cluster. For that we have using velero(--restic). .
but did not get chance to take pod volumes.
Any one please look into this.
command: velero backup create bkp4 --include-namespaces cicd-dev --snapshot-volumes
OutPut:

and restic DeamonSet :

gkdba87 on 18 Jun 2019

What object storage system are you using? Can you also provide the output of velero restic repo get -o yaml?

skriss on 18 Jun 2019

@skriss , i have used IBM S3 Object storage.
Output of restic repo :

gkdba87 on 19 Jun 2019

oh, it looks like there are no pods for the restic daemonset...do you have any node taints that are preventing pods from being scheduled on each node?

skriss on 19 Jun 2019

@skriss No , i didn't taint any nodes. My K8 cluster have different types of node flavors like suse-linux-nodes and IBM-Z-linux nodes. so that I have use Node-selector to spin the pods in Suse-linux .

gkdba87 on 19 Jun 2019