-
Notifications
You must be signed in to change notification settings - Fork 1
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
CASMINST-5103 Better LVM logging #48
Conversation
This could change to also fail out and link to the wipe document if volume groups still exist. Maybe even just trigger the emergency shell with directions for continuing the boot afterwards.. but that's fancy. |
Might be worth it. Otherwise, it'll continue to boot and the problem won't be obvious? |
The pave function doesn't report to the console whether or not any volume groups were found, let alone which logical volumes were removed. This change adds discovered volume groups and removed items to the console.
I tested the failure commands on two nodes that were already booted:
This could use a full boot test though. |
If any given volume group that was deleted still exists, fail the boot with an error. In the error message mention next steps.
Summary and Scope
Issue Type
CASMINST-5103 was difficult to debug because at the moment of failure there was no logging output available. Had the node booted in
rd.debug
orrd.info
mode there might've been more. However we need to see more during the initial boot, and that boot does not run inrd.debug
norrd.info
mode.This change adds discovered volume groups and removed items to the
console, which would be very helpful to see if CASMINST-5103 were to occur again.
Output from a clean boot on a worker node:
Output from a clean boot on a storage node:
Prerequisites
Idempotency
Risks and Mitigations