Red Hat Bugzilla – Bug 1462167
[Docs][SHE] Self hosted engine should only be rebooted after disabling global maintenance if kernel update was performed (re-order steps)
Last modified: 2017-08-08 02:35:01 EDT
Description of problem:
it is not clear that customers should disable global maintenance before rebooting hosted engine
Version-Release number of selected component (if applicable):
2e. Update the base operating system:
# yum update
If any kernel packages were updated, reboot the virtual machine to complete the update.
3. Disable global maintenance. Right-click a self-hosted engine host and select Disable Global HA Maintenance.
So let's summarized
if the point 2e is located before point 3,
that means (according the ascending order ) the reboot operation should be triggered before disable global maintenance.
Can we highlight somehow that we should disable global maintenance prior to reboot?
thank you in advance
Assigning to Avital for review.
Avital, for this bug it seems we just need to switch the order of some steps.
Updated Self-Hosted Engine Guide 4.1: