Log file for failed backups does not exist

[neginhsobhani]

I wanted to debug and find the cause of a backup failure in my kubernetes cluster. I used velero describe backup <backup_name> and came across this:

So as said in the above image I ran velero backup logs <backup_name> to check the logs file for debugging purpose. But I got this as the result:

No log file exists!! I also tested this for other failed backups and got the same result. It seems that velero doesn't save the logs file in case of backup failure. Can anyone tell me why this happens? Is this behavior normal?

I did understand the result of backup failure by using the following command:

kubectl --context prod -n velero get backup/<backup_name> -o yaml 

But the problem with velero not saving logs file still exists.

Environment:

• Velero version: v1.12.2
• Kubernetes version: v1.28.4
• OS: ubuntu 22.04

[Lyndon-Li]

Can you share the cause of backup failure?

[neginhsobhani]

@Lyndon-Li The cause of backup is that the object storage which I use for storing backups was not available at that moment as you can see in the below image:

[neginhsobhani]

@codecov @konstantin @dzaninovic
hello, can you please help with this issue?

[Lyndon-Li]

Velero saves the logs into the backup storage, if the backup storage is not available, the backup will fail and the logs for the backup will not be saved either.

[neginhsobhani]

Velero saves the logs into the backup storage, if the backup storage is not available, the backup will fail and the logs for the backup will not be saved either.

Yes, that makes sense. Thanks for answering 🙏