The documentation [1] states, that if fencing and kdump integration are enabled on an existing host, a host reinstall is required. However, there is no indication for this in UI. Assuming documentation is correct, we should let the user know that host reinstall is required to enjoy the kdump intergration functionality. It can be a warning sign and a tool tip with explanation. Current behavior confuses the users and prevents us from getting the required information from the first attempt. [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-host_tasks#Configuring_Host_Power_Management_Settings
(In reply to Marina from comment #0) > The documentation [1] states, that if fencing and kdump integration are > enabled on an existing host, a host reinstall is required. > However, there is no indication for this in UI. > > Assuming documentation is correct, we should let the user know that host > reinstall is required to enjoy the kdump intergration functionality. It can > be a warning sign and a tool tip with explanation. Current behavior confuses > the users and prevents us from getting the required information from the > first attempt. > > [1] > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/ > html/administration_guide/sect- > host_tasks#Configuring_Host_Power_Management_Settings This is not true, below warning is save in audit log and showed in Events tab on 1. Each activation of the host 2. If you enable Kdump integration in Power Management tab when you edit a host Please take a look at customer logs, they are plenty of those warnings: 2017-09-07 07:26:23,745-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler5) [7834553c] EVENT_ID: KDUMP_DETECTION_NOT_CONFIGURED_ON_VDS(617), Correlation ID: 7834553c, Call Stack: null, Custom Event ID: -1, Message: Kdump integration is enabled for host host1.example.com, but kdump is not configured properly on host. Anyway it seems that customers completely ignores warnings, so we would need to prioritize BZ1480433.
Martin, indeed, I see this warning in the events log: "Kdump integration is enabled for host rhevh-26.gsslab.rdu2.redhat.com, but kdump is not configured properly on host." However: 1. The warning does not say that restart is required. 2. No indication on the host itself. 3. No one except support look into the logs. Read: customers would not go to logs to see if operation performed in UI is successful. It should result in a feedback in the same place it was issued, i.e. the UI. Maybe we should close this bug as duplicate of the one you pointed to. Or, we can keep this one to request to adjust the text of the warning in the Events log, to make it more clear that reinstall of the host is needed. (reinstall, really? not restart?)
*** Bug 1480433 has been marked as a duplicate of this bug. ***
Marina, kdump is not the only configuration that needs the host to be re-installed, there is also the iommu stuff for example. I think bugzilla #1480433 was a more general approach. This current BZ is just for kdump, so subset of the other BZ. We should close this one as DUP and keep the other, the other way around, to get a more comprehensive solution instead of opening BZs for every single setting that needs a host to be re-installed.... What do you think?
(In reply to Marina from comment #2) > Martin, indeed, I see this warning in the events log: > "Kdump integration is enabled for host rhevh-26.gsslab.rdu2.redhat.com, but > kdump is not configured properly on host." > > However: > 1. The warning does not say that restart is required. Not restart, but Reinstall is required, because we need to add parameters to kdump and restart the service. > 2. No indication on the host itself. > 3. No one except support look into the logs. Read: customers would not go to > logs to see if operation performed in UI is successful. It should result in > a feedback in the same place it was issued, i.e. the UI. As I said this is a WARNING in audit log and it is displayed in Events tab in UI. It's not our fault that customers are ignoring warnings
(In reply to Germano Veit Michel from comment #4) > Marina, kdump is not the only configuration that needs the host to be > re-installed, there is also the iommu stuff for example. I think bugzilla > #1480433 was a more general approach. This current BZ is just for kdump, so > subset of the other BZ. We should close this one as DUP and keep the other, > the other way around, to get a more comprehensive solution instead of > opening BZs for every single setting that needs a host to be > re-installed.... What do you think? Completely agree with the above, I've just reopened BZ1480433 and closing this one as duplicate of BZ1480433. *** This bug has been marked as a duplicate of bug 1480433 ***