Ark backups stopped being performed #27
Labels
No Label
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#27
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The last backups are from May 27
The
BackupStorageLocation
is invalid according to the logs, but it does look valid.I thought I had fixed it by recreating the BackupStorageLocation resource, but I had restarted the pod before it was recreated, so the pod ran successfully without any BackupStorageLocation
There isn't much in a BackupStorageLocation:
I am still working on it
I ended up switching to Velero 1.0 (Ark got renamed at version 0.11) using the new installation process that's part of the velero binary and using a new bucket. I could not figure out what was wrong with the current bucket. The same error was happening with velero as it did with our previous Ark setup.
I have executed a manual backup, now we need to wait until the next automated backup takes place to confirm everything works again before we can close this
Hooray, that did the trick:
And the matching snapshots: https://console.cloud.google.com/compute/snapshots?organizationId=772167872692&project=fluted-magpie-218106&tab=snapshots&snapshotssize=50
I have also deleted the heptio-ark namespace and the matching service account and IAM. Closing this one