Bug 1614657
Summary: | [downstream clone - 4.2.6] Kdump Status is disabled after successful fencing of host. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.4 | CC: | amarchuk, lsurette, lsvaty, mgoldboi, mperina, pmatyas, Rhev-m-bugs, srevivo, tburke, ycui |
Target Milestone: | ovirt-4.2.6 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | v4.20.39 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1607952 | Environment: | |
Last Closed: | 2018-09-04 13:43:24 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: | 1607952 | ||
Bug Blocks: |
Description
RHV bug bot
2018-08-10 07:17:30 UTC
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) Verified on vdsm-4.20.39-1.el7ev.x86_64 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 |