Bug 1582590 - Supervdsmd.lock file missing after a reboot
Summary: Supervdsmd.lock file missing after a reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: bipin
URL:
Whiteboard:
Depends On: 1534197 1582595
Blocks: 1520836
TreeView+ depends on / blocked
 
Reported: 2018-05-25 17:02 UTC by bipin
Modified: 2019-05-20 04:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1582595 (view as bug list)
Environment:
Last Closed: 2019-05-20 04:55:15 UTC
Embargoed:

Attachments (Terms of Use)

Description bipin 2018-05-25 17:02:11 UTC 
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:
Comment 6 bipin 2018-07-26 10:50:07 UTC 
Moving the bug as verified since the issue seems to be fixed.
Also,since the bug was not re-producible always will open if seen again.


Steps:
=====
1.Rebooted the RHVH nodes
2.The vdsm directory was present under /var/run

Component:
=========
vdsm-4.20.35-1.el7ev.x86_64
rhv 4.2.5.2
Note You need to log in before you can comment on or make changes to this bug.