-
Notifications
You must be signed in to change notification settings - Fork 72
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
Add final upgrade step to check if reboot needed #773
Conversation
@@ -87,6 +87,7 @@ class PostUpgradeChecks < Abstract | |||
def compose | |||
add_steps(find_checks(:default)) | |||
add_steps(find_checks(:post_upgrade)) | |||
add_step(Procedures::Packages::CheckForReboot) |
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.
why isn't the step just tagged with post_upgrade
?
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.
I want it to be the final step so the user sees it.
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.
Hence my question above:
My only concern is whether this is too "hidden" of output for the user and if instead we need more of special post upgrade output (similar to the installer) that clearly articulates any upgrade considerations.
a449838
to
80f3c77
Compare
80f3c77
to
0c989c4
Compare
0c989c4
to
f6b31c7
Compare
Here is the updated output:
I am not the biggest fan of that "what does warning mean" output, but we can live with it. |
I could look into introducing a different output for this to add before or after this change? Maybe that's a bigger follow up to tackle as part of some overall changes. |
I learned that this results in an exit code |
If they take notice, this is what we wanted, no? :) (Didn't you yourself pondered about an exit code at some point?) |
This is intended to automate into the procedure and be able to drop from our documentation running the command explicitly. I have included example outputs below. My only concern is whether this is too "hidden" of output for the user and if instead we need more of special post upgrade output (similar to the installer) that clearly articulates any upgrade considerations.
Output if reboot needed:
Example if no reboot: