+++ This bug is a downstream clone. The original bug is: +++
+++ bug 1607952 +++
======================================================================
Description of problem:
After successful fencing of Kdump Enabled host, Kdump status changes to Disabled state.
Version-Release number of selected component (if applicable):
rhvm-4.2.4.5-0.1.el7_3.noarch
How reproducible:
Always
Steps to Reproduce:
1. Enable kdump and check Kdump Status and confirm if it is Enabled.
2. Fence host
3. Check Kdump Status again
Actual results:
Kdump status Disabled.
Expected results:
Kdump status should be Enabled.
Additional info:
Refresh host capabilities changes correctly show Kdump status as Enabled.
(Originally by Ameya Charekar)
Looking at the logs it seems that VDSM was started at
Jul 19 12:33:56 bb03-rhv06 systemd: Started Virtual Desktop Server Manager
and GetCaps call from engine was returned at
2018-07-19 12:34:11,321+0200 INFO (jsonrpc/7) [api.host] FINISH getCapabilities
but Kdump server started later:
Jul 19 12:36:27 bb03-rhv06 kdumpctl: kexec: loaded kdump kernel
Jul 19 12:36:27 bb03-rhv06 kdumpctl: Starting kdump: [OK]
so GetCaps call return Kdump is not available on host. So we will need to add explicit dependency on kdump service to vdsmd service.
This issue could be workarounded by putting host to Maintenance and Activating it again manually after successfull engine restart.
(Originally by Martin Perina)
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/RHEA-2018:2624