Thanks for your post. There are many updates which require reboot of target server to finish applying update. If you don't reboot the target server, that update will not be applied to the server. You will be able to send the update to the server but it will only apply next time the server is rebooted. In short, you are not really applying that update in that case.
OME will reboot the server only if the update needs a reboot. If the update can be applied without a reboot it will be applied and server will not be rebooted even if you have checked the box.
If it is not checked by default, customers may forget to check it as users typically go with default options. In that case, most of the updates will not be successful.
We can look at making that option configurable for future releases. That way you can choose whether to have the box checked or unchecked by default.
Thanks for the reply. I understand that many updates require a reboot and that customers could forget. However at present, if you forget to untick 'reboot' you could risk rebooting a live server. If off was the default, the worst would be that you wouldn't apply the update. This a much safer default in my opinion. (Plus you can easily tell if your updates have been applied in OME anyhow so customers should still notice.)
Making the option configurable sounds like a plan.
On the subject of OME only rebooting the box if the update requires it, this feature would be much more useful if OME coudl tell you that a certain set of updates would or would not require a reboot BEFORE you apply them.
Typically updates are scheduled during maintenance windows and servers are expected to reboot during that. As you mentioned it may not always be the case and making it configurable might help.
The information regarding reboot is not always available before applying the update. After the update is applied the return code from the updates tells OME whether the server needs a reboot for that update. We can look at adding some context sensitive help describing which updates typically need reboot.
DELL-Abhijit P
Community Manager
•
711 Posts
0
July 12th, 2012 08:00
Hi Nick,
Thanks for your post. There are many updates which require reboot of target server to finish applying update. If you don't reboot the target server, that update will not be applied to the server. You will be able to send the update to the server but it will only apply next time the server is rebooted. In short, you are not really applying that update in that case.
OME will reboot the server only if the update needs a reboot. If the update can be applied without a reboot it will be applied and server will not be rebooted even if you have checked the box.
If it is not checked by default, customers may forget to check it as users typically go with default options. In that case, most of the updates will not be successful.
We can look at making that option configurable for future releases. That way you can choose whether to have the box checked or unchecked by default.
Regards
Abhijit
nick-h
25 Posts
0
July 12th, 2012 08:00
Hi Abhijit,
Thanks for the reply. I understand that many updates require a reboot and that customers could forget. However at present, if you forget to untick 'reboot' you could risk rebooting a live server. If off was the default, the worst would be that you wouldn't apply the update. This a much safer default in my opinion. (Plus you can easily tell if your updates have been applied in OME anyhow so customers should still notice.)
Making the option configurable sounds like a plan.
On the subject of OME only rebooting the box if the update requires it, this feature would be much more useful if OME coudl tell you that a certain set of updates would or would not require a reboot BEFORE you apply them.
Cheers
Nick
DELL-Abhijit P
Community Manager
•
711 Posts
0
July 12th, 2012 09:00
Thanks for the feedback Nick.
Typically updates are scheduled during maintenance windows and servers are expected to reboot during that. As you mentioned it may not always be the case and making it configurable might help.
The information regarding reboot is not always available before applying the update. After the update is applied the return code from the updates tells OME whether the server needs a reboot for that update. We can look at adding some context sensitive help describing which updates typically need reboot.
Regards
Abhijit