Bug 1613339
| Summary: | Stop/Start VDO service during host Maintenance/Activate | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Gobinda Das <godas> | |
| Component: | Backend.Core | Assignee: | Kaustav Majumder <kmajumde> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.2.6 | CC: | bugs, guillaume.pavese, jcall, kmajumde, sabose | |
| Target Milestone: | ovirt-4.2.7 | Flags: | rule-engine:
ovirt-4.2+
|
|
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.2.7.2 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1619635 (view as bug list) | Environment: | ||
| Last Closed: | 2018-11-02 14:38:08 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1619635 | |||
|
Description
Gobinda Das
2018-08-07 12:21:06 UTC
Here is /var/log/messages: Jul 20 09:48:14 rhsdev-grafton2 vdo: vdo: ERROR - Kernel module kvdo not installed Jul 20 09:48:14 rhsdev-grafton2 vdo: ERROR - Kernel module kvdo not installed Jul 20 09:48:14 rhsdev-grafton2 vdo: vdo: ERROR - Kernel module kvdo not installed Jul 20 09:48:14 rhsdev-grafton2 vdo: ERROR - Kernel module kvdo not installed Jul 20 09:48:14 rhsdev-grafton2 vdo: ERROR - modprobe: FATAL: Module kvdo not found. Jul 20 09:48:14 rhsdev-grafton2 vdo: vdo: ERROR - modprobe: FATAL: Module kvdo not found. Jul 20 09:48:14 rhsdev-grafton2 vdo: Starting VDO vdo_sdd1 Jul 20 09:48:14 rhsdev-grafton2 vdo: Starting VDO vdo_sdb Jul 20 09:48:14 rhsdev-grafton2 systemd: vdo.service: main process exited, code=exited, status=2/INVALIDARGUMENT Jul 20 09:48:14 rhsdev-grafton2 systemd: Failed to start VDO volume services. Jul 20 09:48:14 rhsdev-grafton2 systemd: Dependency failed for /gluster_bricks/engine. Jul 20 09:48:14 rhsdev-grafton2 systemd: Job gluster_bricks-engine.mount/start failed with result 'dependency'. Jul 20 09:48:14 rhsdev-grafton2 systemd: Dependency failed for /gluster_bricks/hdd. Jul 20 09:48:14 rhsdev-grafton2 systemd: Job gluster_bricks-hdd.mount/start failed with result 'dependency'. Jul 20 09:48:14 rhsdev-grafton2 systemd: Dependency failed for /gluster_bricks/vmstore. Jul 20 09:48:14 rhsdev-grafton2 systemd: Job gluster_bricks-vmstore.mount/start failed with result 'dependency'. Jul 20 09:48:14 rhsdev-grafton2 systemd: Dependency failed for /gluster_bricks/data. Jul 20 09:48:14 rhsdev-grafton2 systemd: Job gluster_bricks-data.mount/start failed with result 'dependency'. Jul 20 09:48:14 rhsdev-grafton2 systemd: Dependency failed for /gluster_bricks/hddvol/hdd. Jul 20 09:48:14 rhsdev-grafton2 systemd: Job gluster_bricks-hddvol-hdd.mount/start failed with result 'dependency'. Jul 20 09:48:14 rhsdev-grafton2 systemd: Unit vdo.service entered failed state. Jul 20 09:48:14 rhsdev-grafton2 systemd: vdo.service failed. The system was upgraded while VDO service was running which was causing mounting device issue. In lsblk command output there was no filesystems were not mounted, and the LV is not available. https://gerrit.ovirt.org/#/c/93776/ seems to be missing backport to 4.2, moving back to post for cross checking. Created patch for backporting to 4.2 https://gerrit.ovirt.org/#/c/94394/ Tested with ovirt-engine-4.2.7.2 When the host is moved in to maintenance by stopping the gluster services from RHV Manager UI, the gluster and VDO services are stopped. When the host is activated, gluster and VDO services are started again This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |