Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1582595

Summary:	Supervdsmd.lock file missing after a reboot
Product:	[oVirt] vdsm	Reporter:	bipin <bshetty>
Component:	SuperVDSM	Assignee:	Martin Perina <mperina>
Status:	CLOSED DUPLICATE	QA Contact:	Raz Tamir <ratamir>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.30.0	CC:	bugs, mperina, rbarry, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone:	ovirt-4.2.4	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1582590	Environment:
Last Closed:	2018-06-01 09:46:14 UTC	Type:	Bug
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:
Bug Blocks:	1582590

Description bipin 2018-05-25 17:10:01 UTC

+++ This bug was initially created as a clone of Bug #1582590 +++

Description of problem:
After a reboot, the supervdsmd.lock file goes missing. This is seen only after a reboot.Due to which the vdsmd service and its dependency services goes in inactive state.
Current workaround is creating a supervdsmd.lock file under /var/run/vdsm.


Version-Release number of selected component (if applicable):
vdsm-4.20.28-1.el7ev.x86_64
redhat-release-virtualization-host-4.2-3.0.el7.x86_64


How reproducible:
3/5

Steps to Reproduce:
1. Have the RHVH installed on the hosts
2. Reboot the node
3. Check the "systemctl status vdsmd" . Its fails

Actual results:
The supervdsmd.lock file goes missing

Expected results:
The supervdsmd.lock  shouldnt go missing

Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-05-25 13:02:14 EDT ---

This bug is automatically being proposed for the current release of Red Hat Hyperconverged Infrastructure (RHHI) under active development, by setting the release flag 'rhhi‑2.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

--- Additional comment from bipin on 2018-05-25 13:03:07 EDT ---

[root@rhsqa-grafton7-nic2 ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)

May 21 13:16:06 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Dependency failed for Virtual Desktop Server Manager.
May 21 13:16:06 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Job vdsmd.service/start failed with result 'dependency'.
May 21 13:50:19 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Dependency failed for Virtual Desktop Server Manager.
May 21 13:50:19 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Job vdsmd.service/start failed with result 'dependency'.
May 21 13:53:00 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Dependency failed for Virtual Desktop Server Manager.
May 21 13:53:00 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Job vdsmd.service/start failed with result 'dependency'.
May 21 14:00:09 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Dependency failed for Virtual Desktop Server Manager.
May 21 14:00:09 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Job vdsmd.service/start failed with result 'dependency'.
[root@rhsqa-grafton7-nic2 ~]# systemctl start vdsmd
A dependency job for vdsmd.service failed. See 'journalctl -xe' for details.
[root@rhsqa-grafton7-nic2 ~]# journalctl -xe
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6653]: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 251, in main
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6653]: __assertSingleInstance()
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6653]: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 246, in __assertSingleInstance
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6653]: raise FatalError(str(e))
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6653]: vdsm.supervdsm_server.FatalError: [Errno 2] No such file or directory: '/var/run/vdsm/supervdsmd.lock'
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service: main process exited, code=exited, status=1/FAILURE
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Unit supervdsmd.service entered failed state.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service failed.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service holdoff time over, scheduling restart.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Started Auxiliary vdsm service for running helper functions as root.
-- Subject: Unit supervdsmd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit supervdsmd.service has finished starting up.
-- 
-- The start-up result is done.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Starting Auxiliary vdsm service for running helper functions as root...
-- Subject: Unit supervdsmd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit supervdsmd.service has begun starting up.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com supervdsmd[6668]: Supervdsm failed to start: [Errno 2] No such file or directory: '/var/run/vdsm/supervdsmd.lock'
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com python2[6668]: detected unhandled Python exception in '/usr/share/vdsm/supervdsmd'
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com abrt-server[6679]: Not saving repeating crash in '/usr/share/vdsm/supervdsmd'
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: Traceback (most recent call last):
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: File "/usr/share/vdsm/supervdsmd", line 24, in <module>
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: supervdsm_server.main(sys.argv[1:])
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 251, in main
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: __assertSingleInstance()
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 246, in __assertSingleInstance
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: raise FatalError(str(e))
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com daemonAdapter[6668]: vdsm.supervdsm_server.FatalError: [Errno 2] No such file or directory: '/var/run/vdsm/supervdsmd.lock'
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service: main process exited, code=exited, status=1/FAILURE
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Unit supervdsmd.service entered failed state.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service failed.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service holdoff time over, scheduling restart.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: start request repeated too quickly for supervdsmd.service
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Failed to start Auxiliary vdsm service for running helper functions as root.
-- Subject: Unit supervdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit supervdsmd.service has failed.
-- 
-- The result is failed.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: Unit supervdsmd.service entered failed state.
May 21 14:01:10 rhsqa-grafton7-nic2.lab.eng.blr.redhat.com systemd[1]: supervdsmd.service failed.

Comment 2 Ryan Barry 2018-05-30 16:30:38 UTC

I suspect this is actually a duplicate of rhbz#1534197

RHV-H does not modify vdsm or its startup in any way which would affect this. I cannot reproduce, and there is nothing in the logs which indicates RHVH is blocking it in any way.

Comment 3 Martin Perina 2018-06-01 09:46:14 UTC

(In reply to Ryan Barry from comment #2)
> I suspect this is actually a duplicate of rhbz#1534197
> 
> RHV-H does not modify vdsm or its startup in any way which would affect
> this. I cannot reproduce, and there is nothing in the logs which indicates
> RHVH is blocking it in any way.

Make sense, closing as duplicate

*** This bug has been marked as a duplicate of bug 1534197 ***