-
Notifications
You must be signed in to change notification settings - Fork 341
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
Backup selection bugfix #1701
Backup selection bugfix #1701
Conversation
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 3m 56s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 20s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 59s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 00s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 22s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 3m 47s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 30s |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 3m 50s |
recheck |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
1610a56
to
4306fd5
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 36s |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 5m 26s |
Backport to stable-6: 💚 backport PR created✅ Backport PR branch: Backported as #1710 🤖 @patchback |
Backup selection bugfix SUMMARY Fix bug in backup_selection where an existing backup selection was not updated to add Conditions if that value was previously empty. ISSUE TYPE Bugfix Pull Request COMPONENT NAME backup_selection ADDITIONAL INFORMATION Split into two commits, the first commit adds comprehensive integration tests to cover the scenarios that were failing and the second commit fixes the code. Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Alina Buzachis (cherry picked from commit 19b89f6)
Backup selection bugfix SUMMARY Fix bug in backup_selection where an existing backup selection was not updated to add Conditions if that value was previously empty. ISSUE TYPE Bugfix Pull Request COMPONENT NAME backup_selection ADDITIONAL INFORMATION Split into two commits, the first commit adds comprehensive integration tests to cover the scenarios that were failing and the second commit fixes the code. Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Alina Buzachis (cherry picked from commit 19b89f6)
Backup selection bugfix SUMMARY Fix bug in backup_selection where an existing backup selection was not updated to add Conditions if that value was previously empty. ISSUE TYPE Bugfix Pull Request COMPONENT NAME backup_selection ADDITIONAL INFORMATION Split into two commits, the first commit adds comprehensive integration tests to cover the scenarios that were failing and the second commit fixes the code. Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Alina Buzachis
Backup selection bugfix SUMMARY Fix bug in backup_selection where an existing backup selection was not updated to add Conditions if that value was previously empty. ISSUE TYPE Bugfix Pull Request COMPONENT NAME backup_selection ADDITIONAL INFORMATION Split into two commits, the first commit adds comprehensive integration tests to cover the scenarios that were failing and the second commit fixes the code. Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Alina Buzachis (cherry picked from commit 19b89f6)
…/stable-6/19b89f682227f8755322250c929355812dc37a2c/pr-1701 [PR #1701/19b89f68 backport][stable-6] Backup selection bugfix
SUMMARY
Fix bug in backup_selection where an existing backup selection was not updated to add Conditions if that value was previously empty.
ISSUE TYPE
COMPONENT NAME
backup_selection
ADDITIONAL INFORMATION
Split into two commits, the first commit adds comprehensive integration tests to cover the scenarios that were failing and the second commit fixes the code.