Aller au contenu

BackupPartiallyFailedGitea#

This alert is used to indicate all the failure of Velero backup of Gitea.

Solutions#

  • Check if cluster was available when error occured ( new zone deployment pending). It is possible for an action on the service to trigger backup errors.

For information, next automated backup will be performed in 24h.

  • See the description of backups using : velero describe backups <backup-name>

Example :

toolbox install velero
velero backup get # List Backups
velero backup get | grep -v Completed # output backups that are not OK
velero backup describe gitea-daily-schedule-20201123020047 # exp: description of specific backups
velero backup logs gitea-daily-schedule-20201123020047 # Retrieve Backup Logs

  • Check if velero's pods are running : kubectl get pod -n velero

  • Manually launch a Velero backup for Gitea, to see if the problem persists:

velero backup create "backup-gitea-test" --include-namespaces gitea --snapshot-volumes=true`

Note

If it is possible to manualy create a backup, it means the problem is not present anymore.

False alarm Logs

Example of logs that indicate this alert it's a false alarm.

  • error indicating an issue wist summary message and not with the backup itself: 
    velero backup logs gitea-daily-schedule-20210428020003|grep -v 'info'
...
stderr=: unable to find summary in restic backup command output"