qiuming-best
commented
1 year ago @nwakalka the logs you provided are incomplete, could you generate the debug bundle with the command velero debug --backup $backupName and uploaded it in this issue?
Closed nwakalka closed 11 months ago
qiuming-best
commented
1 year ago @nwakalka the logs you provided are incomplete, could you generate the debug bundle with the command velero debug --backup $backupName and uploaded it in this issue?
nwakalka
commented
1 year ago Hi @qiuming-best ,
We are facing an error while getting debug bundle.
nikhil@nikhil-virtual-machine:~/Downloads/SFS/nwakalka$ oc get deployments -n mcs-backup
NAME READY UP-TO-DATE AVAILABLE AGE
mcs-velero 1/1 1 1 49d
s3-backup-proxy 3/3 3 3 49d
nikhil@nikhil-virtual-machine:~/Downloads/SFS/nwakalka$ kubectl exec -it mcs-velero-576f94d5cb-dpwhc -n mcs-backup -- /velero debug --backup ddaily-backup-20230413020006
Defaulted container "mcs-velero" out of: mcs-velero, mcs-velero-plugin-for-aws (init), mcs-velero-plugin-for-azure (init), mcs-plugin-ocp (init)
An error occurred: velero deployment does not exist in namespace: mcs-backup
command terminated with exit code 1
so I changed the deployment from mcs-velero to velero but still facing the same error
nikhil@nikhil-virtual-machine:~/Downloads/SFS/nwakalka$ kubectl get deployments -n mcs-backup
NAME READY UP-TO-DATE AVAILABLE AGE
mcs-velero 0/0 0 0 49d
s3-backup-proxy 3/3 3 3 49d
velero 1/1 1 1 2m50s
nikhil@nikhil-virtual-machine:~/Downloads/SFS/nwakalka$ kubectl get deployments -n mcs-backup velero
NAME READY UP-TO-DATE AVAILABLE AGE
velero 1/1 1 1 3m11s
nikhil@nikhil-virtual-machine:~/Downloads/SFS/nwakalka$ kubectl exec -it velero-7c96c885dd-2k26s -n mcs-backup -- /velero debug --backup daily-backup-20230413020006
Defaulted container "velero" out of: velero, mcs-velero-plugin-for-aws (init), mcs-velero-plugin-for-azure (init), mcs-plugin-ocp (init)
An error occurred: velero deployment does not exist in namespace: mcs-backup
command terminated with exit code 1
@nwakalka it's no need to execute this command in pod, what you need it's just using velero cli to execute in your local machine.
GVOROS
commented
1 year ago @qiuming-best We tried with the velero CLI also, but we got the same issue:
# ./velero-v1.9.3-linux-amd64 -n mcs-backup debug --backup backuptest
An error occurred: velero deployment does not exist in namespace: mcs-backup
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest
An error occurred: velero deployment does not exist in namespace: mcs-backup
# oc get deployment -n mcs-backup
NAME READY UP-TO-DATE AVAILABLE AGE
mcs-velero 1/1 1 1 8d
s3-backup-proxy 2/2 2 2 8d
velero 1/1 1 1 35s
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest
An error occurred: velero deployment does not exist in namespace: mcs-backup
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest --verbose
An error occurred: velero deployment does not exist in namespace: mcs-backup
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest -v 9
An error occurred: velero deployment does not exist in namespace: mcs-backupWe also tried to modify the name of the deployment, but did not help.
qiuming-best
commented
1 year ago @GVOROS your correct generating bundle command should be ./velero-v1.9.3-linux-amd64 debug --backup backuptest
GVOROS
commented
1 year ago @qiuming-best
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest
An error occurred: velero deployment does not exist in namespace: mcs-backupHi @qiuming-best
I was wondering if there has been any progress or updates on the issue? I understand that you may be busy, but I would greatly appreciate any information you could provide.
Thank you in advance.
qiuming-best
commented
1 year ago @nwakalka Sorry for the late response, you need to add a namespace in the command, the complete command would be ./velero-v1.9.3-linux-amd64 debug --backup backuptest -n velero
GVOROS
commented
1 year ago @qiuming-best We do not have velero namespace. As you can see we neither have deployment called velero, instead we have mcs-velero. Can it be a problem?
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest -n velero
An error occurred: velero deployment does not exist in namespace: velero
# ./velero-v1.9.3-linux-amd64 debug --backup backuptest -n mcs-backup
An error occurred: velero deployment does not exist in namespace: mcs-backup
# oc get deployment -n mcs-backup | grep velero
mcs-velero 1/1 1 1 46d@qiuming-best May I ask if you have any updates?
GVOROS
commented
1 year ago Hi @qiuming-best, Do you have any news?
github-actions[bot]
commented
1 year ago This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.
GVOROS
commented
1 year ago Anyone can help us?
github-actions[bot]
commented
11 months ago This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.
github-actions[bot]
commented
11 months ago This issue was closed because it has been stalled for 14 days with no activity.
What steps did you take and what happened:
We are trying to run velero backups for cluster resources but backups are failing.
here you can find backup logs for more info
please find attached velero pod logs for more info
Backup_logs.txt
Our BackupStorageLocation is available and able to connect to our OBS buckets.
What did you expect to happen:
The following information will help us better understand what's going on:
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>to generate the support bundle, and attach to this issue, more options please refer tovelero debug --helpIf you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velerovelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlvelero backup logs <backupname>velero restore describe <restorename>orkubectl get restore/<restorename> -n velero -o yamlvelero restore logs <restorename>Anything else you would like to add:
Environment:
velero version): v1.9.3velero client config get features): NAkubectl version):v1.24.0+3882f8f/etc/os-release): linux/amd64Vote 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.