+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1480433 +++ ====================================================================== Description of problem: For VMs, if the user changes a configuration that requires the VM to be power cycled to take effect, a tooltip is displayed to inform the user. However, the same applies for Hosts but and there is no such feature. Some host configurations require the host to be re-installed in order to be pushed. One example is kdump integration. We have the following note in the Documentation: ~~~ When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 7.5.12, “Reinstalling Hosts”. ~~~ This is not user-friendly. This RFE is to create a similar feature for Hosts. (Originally by Germano Veit Michel)
*** This bug has been marked as a duplicate of bug 1489902 *** (Originally by Marina Kalinin)
There are other options which require host reinstallation such as changing kernel command line parameters of the host or changing type of firewall for the cluster, so I'm reopening this RFE to cover all existing scenarios (Originally by Martin Perina)
*** Bug 1489902 has been marked as a duplicate of this bug. *** (Originally by Martin Perina)
Marina, this is not a bug, this is RFE, because all such changes either shows that somehow or the need to reinstall is described in documentation. Also we are still looking at the scope we don't know yet if we will backport it to 4.1.z. Let's work on it for 4.2 and when done we will see. (Originally by Martin Perina)
Testing on ovirt-engine-4.1.8-0.1.el7.noarch There is no warning of any kind anywhere to notify me that I have to reinstall the host after adding PM agent and enabling kdump.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Verified on ovirt-engine-4.1.8.1-0.1.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3427