+++ This bug was initially created as a clone of Bug #1613339 +++ Description of problem: Now if user will upgrade any host, VDO service is not restarting after upgrade. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: VDO service failed state Expected results: VDO service should be Active/Running state. Additional info: --- Additional comment from Gobinda Das on 2018-08-08 03:12:07 EDT --- 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.
The dependent oVirt bug is ON_QA and moving this bug to ON_QA to enable verification
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
Please provide doc_text
Added doc text.
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:3523