-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update NAB object status appropriately if VeleroBackup already exists for the NAB object #59
Comments
Are we able to reproduce this error constantly ❓ I think we talked about this being a corner case If it is a corner case, would not prioritize it now |
Agree this is corner case as we generate names based on the NAB name, namespace and hash, so it's really corner case to expect VeleroBackup to be there beforehand. |
Right now I get the following status on NAB object if the VeleroBackup object already exists:
I think we should add some msg related to backup already exists etc |
@shubham-pampattiwar now I am confused is not the bug you are worried, but only a feedback message that NAB created Velero Backup ❓ |
We want to keep NAB : VeleroBackup :: 1:1 |
I will try to reproduce this and comment again |
@shubham-pampattiwar can you test this in #73 ? I think the error was related to the race condition I fixed there On your example #59 (comment) it failed here oadp-non-admin/internal/controller/nonadminbackup_controller.go Lines 306 to 315 in 4b2f57f
and on the next reconcile it went here
|
No description provided.
The text was updated successfully, but these errors were encountered: