Bug 1501793

Summary: [downstream clone - 4.1.8] [RFE] Indicate host needs to be reinstalled to push new configurations.
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED ERRATA QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.4CC: lsurette, lveyde, mgoldboi, mkalinin, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, trichard, ykaul, ylavi
Target Milestone: ovirt-4.1.8Keywords: FutureFeature, Reopened, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.1.8.1 Doc Type: Enhancement
Doc Text:
There are several cluster and host settings which require reinstallation of the host if changed. The requirement to reinstall was always mentioned in documentation and a WARNING event was raised. With this release, the Administration Portal now also shows an exclamation mark icon for each host that needs to be reinstalled. When an exclamation mark icon is shown, you can find the details about it in the Action Items section of the host's details view.
Story Points: ---
Clone Of: 1480433 Environment:
Last Closed: 2017-12-12 09:23:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1480433    
Bug Blocks:    

Description rhev-integ 2017-10-13 08:34:37 UTC
+++ 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)

Comment 3 rhev-integ 2017-10-13 08:34:50 UTC

*** This bug has been marked as a duplicate of bug 1489902 ***

(Originally by Marina Kalinin)

Comment 4 rhev-integ 2017-10-13 08:34:57 UTC
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)

Comment 5 rhev-integ 2017-10-13 08:35:03 UTC
*** Bug 1489902 has been marked as a duplicate of this bug. ***

(Originally by Martin Perina)

Comment 6 rhev-integ 2017-10-13 08:35:08 UTC
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)

Comment 9 Petr Matyáš 2017-11-16 16:47:48 UTC
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.

Comment 11 Red Hat Bugzilla Rules Engine 2017-11-21 17:39:58 UTC
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.

Comment 13 Petr Matyáš 2017-11-27 13:37:00 UTC
Verified on ovirt-engine-4.1.8.1-0.1.el7.noarch

Comment 16 errata-xmlrpc 2017-12-12 09:23:28 UTC
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