-
Notifications
You must be signed in to change notification settings - Fork 54
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
Snapshottable recovery system #2032
Conversation
8e59d48
to
ca36a26
Compare
ca36a26
to
533f508
Compare
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
Looks like some unit tests needs to be arranged though.
bc3819b
to
13f422d
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2032 +/- ##
==========================================
- Coverage 72.36% 72.15% -0.21%
==========================================
Files 76 76
Lines 9021 9043 +22
==========================================
- Hits 6528 6525 -3
- Misses 1949 1973 +24
- Partials 544 545 +1 ☔ View full report in Codecov by Sentry. |
13f422d
to
dbf6d97
Compare
Deploy the entire recovery system to the same folder (kernel, initrd and rootfs). During upgrade deploy to a transitional folder and then switch it with the current recovery system and then delete the old one. This makes sure we clean up old recovery systems and don't risk mixing systems during upgrade. Signed-off-by: Fredrik Lönnegren <fredrik.lonnegren@suse.com>
dbf6d97
to
0004d1b
Compare
Deploy the entire recovery system to the same folder (kernel, initrd and rootfs).
During upgrade deploy to a transitional folder and then switch it with the current recovery system and then delete the old one.
This makes sure we clean up old recovery systems and don't risk mixing systems during upgrade.
Fixes #2021