Description of problem:
User should be able to request host reboot as a part of host deployment process. The benefit of it is that if we add functionality to host deploy that requires reboot (e.g. modifying kernel arguments via grubby), it can be done automatically instead of being requested from the user.
The functionality can be optional, with checkbox similar to "Activate host after install" or "Configure host firewall" checkboxes.
Aside from upgrade NGN we currently have no use-case that requires host reboot after deployment. When doing NGN upgrade we indeed reboot the host.
This RFE is relevant only once we add, or plan to add the functionality you're talking about that requires exposing a reboot to the user / automatically. Do you have such a use-case at the moment?
If not, I suggest to close this one for now, and re-open once needed.
We have #1301104 and it would be preferable to have the reboot available at the same time.
(In reply to Oved Ourfali from comment #1)
> Aside from upgrade NGN we currently have no use-case that requires host
> reboot after deployment. When doing NGN upgrade we indeed reboot the host.
> This RFE is relevant only once we add, or plan to add the functionality
> you're talking about that requires exposing a reboot to the user /
> automatically. Do you have such a use-case at the moment?
there are 2 use cases I know of:
1) bug 1301104 implements a kernel editing, for that to take effect you need to reboot
2) for upgrading the packages (I don't quite know whether we do yum update vdsm or general update) when e.g. kernel is upgraded the reboot is mandatory. I would strongly advocate for rebooting always as there is no way for us to know when it is or it is not needed.
If we don't upgrade all packages then anyway the functionality is not correct as all the vdsm/qemu/libvirt packages are only tested against latest applied zstream. So I believe we should by default upgrade all packages and by default reboot
It's a bit too late for 4.0 probably, but we should fix it soon
What's the question?
When will it be done?
yeah, I guess. Given the use cases we shouldn't postpone it for too long
Design question: how does the user know if he should or shouldn't ask for a reboot?
I kinda remember some packages have something that say if a reboot is required.
Certainly if we edit the kernel cmdline we can 'remember' that a reboot is required.
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
ok, closing. Please reopen if still relevant/you want to work on it.