-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix reset #565
Conversation
Seems like witht he older ghw, we were not receiving all the proper partitions and mountpoints and such, so on reset we could blindily try to unmount all partitions and call it a day. But now we get info about all of them, so doing so will even unmount the current recovery partition, where the reset source is at, thus failing the reset copy. This patch fixes it by instead of going crazy, making sure we have an order mount/unmount of the proper places at the proper times and we restore everything as is once we are done with it Signed-off-by: Itxaka <itxaka@kairos.io>
These errors would have helped us fixing it. Can we print those errors too?
using some logger preferably |
actually, just return the error (wrapped or not). |
tbh, I would like to do this in a different PR if possible> As it can introduce new errors and I want this to fix the actual reset issue before breaking it further lol |
Signed-off-by: Itxaka <itxaka@kairos.io>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #565 +/- ##
==========================================
+ Coverage 49.73% 49.80% +0.06%
==========================================
Files 48 48
Lines 4588 4582 -6
==========================================
Hits 2282 2282
+ Misses 2029 2026 -3
+ Partials 277 274 -3 ☔ View full report in Codecov by Sentry. |
Seems like witht he older ghw, we were not receiving all the proper partitions and mountpoints and such, so on reset we could blindily try to unmount all partitions and call it a day.
But now we get info about all of them, so doing so will even unmount the current recovery partition, where the reset source is at, thus failing the reset copy.
This patch fixes it by instead of going crazy, making sure we have an order mount/unmount of the proper places at the proper times and we restore everything as is once we are done with it