velero install does not wait for velero to be healthy and does not report errors
#3,861 opened on Jun 9, 2021
Repository metrics
- Stars
- (10,111 stars)
- PR merge metrics
- (PR metrics pending)
Description
What steps did you take and what happened: Did a velero install, but there is an error pulling the image.
$ kubectl get all -n velero
NAME READY STATUS RESTARTS AGE
pod/restic-58jtz 0/1 ContainerCreating 0 11s
pod/velero-5b9775799f-pt7w4 0/1 Init:ErrImagePull 0 11s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/restic 1 1 0 1 0 <none> 11s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/velero 0/1 1 0 11s
NAME DESIRED CURRENT READY AGE
replicaset.apps/velero-5b9775799f 1 1 0 11s
Velero install returned with no errors.
This can easily be reproduced by giving a bad image name.
What did you expect to happen:
Error that the installation is not coming up
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
kubectl logs deployment/velero -n velero Error from server (BadRequest): container "velero" in pod "velero-5b9775799f-pt7w4" is waiting to start: PodInitializing
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.
- :+1: for "I would like to see this bug fixed as soon as possible"
- :-1: for "There are more important bugs to focus on right now"