-
Notifications
You must be signed in to change notification settings - Fork 84
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
[RHELC-1154] Try to rollback all changes even if one of them fails #912
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #912 +/- ##
==========================================
+ Coverage 93.78% 94.24% +0.45%
==========================================
Files 47 47
Lines 4345 4341 -4
Branches 769 768 -1
==========================================
+ Hits 4075 4091 +16
+ Misses 192 174 -18
+ Partials 78 76 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
379369c
to
25bc6ef
Compare
25bc6ef
to
9c11476
Compare
/packit test --labels tier0 |
Ready for review. I believe codecov's warning about coverage of the patch is due to an old version of coverage. When run locally, there is only one line (not in the patch) which is uncovered in pkghandler.py whereas the output of the github Action shows multiple uncovered lines. Coverage report for backup.py locally: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Haven't tested that in a VM yet, but made one comment about what we want to log in case of error.
/packit test --labels tier0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM just needs unit tests rebased
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me.
b68c091
to
0f6e925
Compare
Rebased. |
/packit build --labels tier0 |
/packit test --labels tier0 |
/packit retest-failed |
1 similar comment
/packit retest-failed |
@abadger, the test failures here are not related to the code changes you did? Haven't gone through them yet, just asking here first to see if you had the chance to take a look at it first. |
* Previously, if a RestorableChange managed by BackupController raised an exception on restore, then we would stop rollback. This change makes it so we try to restore every change even if previous ones have failed. * Add the name of the RestorableChange which failed. We can retrieve the class name from the Change instance to display in the error message. This isn't perfect but it identifies where the error occurred a little better than just the exception message. Thanks to Rodolfo for suggesting this. Co-authored-by: Preston Watson <prwatson@redhat.com>
43e31dd
to
1ad3697
Compare
Rebased. (Note: I haven't merged this myself because I don't know how it interacts with the release schedule. Feel free to merge when the time is right). |
Thanks, @abadger. Merging. |
Previously, if a RestorableChange managed by BackupController raised an exception on restore, then we would stop rollback. This change makes it so we try to restore every change even if previous ones have failed.
Jira Issues: RHELC-1154
Checklist
[RHELC-]
is part of the PR titleRelease Pending
if relevant