Bug 1076889

Summary: vdsm3 service doesn't start on rhel7
Product: Red Hat Enterprise Virtualization Manager Reporter: Ohad Basan <obasan>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.4.0CC: abaron, aberezin, bazulay, danken, dougsland, eedri, gklein, iheim, jbiddle, lpeer, obasan, oourfali, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard: infra
Fixed In Version: vdsm3-4.14.5-1.el7 Doc Type: Bug Fix
Doc Text:
Previously, attempting to start vdsm3 on a Red Hat Enterprise Linux 7 host would cause the vdsm daemon to crash instantly. This was caused by missing sanlock and sanlock-python requirements. Now, vdsm3 will run correctly on Red Hat Enterprise Linux 7 hosts.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-09 13:29:34 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: 1064042    
Bug Blocks: 1064038    

Description Ohad Basan 2014-03-16 09:58:10 UTC
Description of problem:

after host deploy on rhel7.
vdsmd starts and instantly crashes
supervdsmd tries to spawn it and fails continuously.
attaching the supervdsm log.
the vdsm.log itself is empty

Comment 3 Douglas Schilling Landgraf 2014-03-17 21:49:06 UTC
Hi Ohad,

I have reproduced your report, for while you could run yum install sanlock-python and try to restart the vdsm daemon. I will sync vdsm3 with last 3.4 upstream build and update here.

Comment 9 Ohad Basan 2014-03-23 10:35:29 UTC
vdsm3 now starts successfully. but still the engine is failing to communicate with the host
it requires another bug which I'll open

Comment 11 Jiri Belka 2014-04-15 09:26:35 UTC
ok, vdsm3-4.14.5-1.el7ev.x86_64

[root@dell-r210ii-03 1.el7ev]# systemctl get-default
multi-user.target
[root@dell-r210ii-03 1.el7ev]# ls -l /etc/systemd/system/multi-user.target.wants/vdsm*
lrwxrwxrwx. 1 root root 37 Apr 15 13:12 /etc/systemd/system/multi-user.target.wants/vdsmd.service -> /usr/lib/systemd/system/vdsmd.service
[root@dell-r210ii-03 1.el7ev]# ls -l /usr/lib/systemd/system/vdsmd.service 
-rw-r--r--. 1 root root 656 Mar 20 20:05 /usr/lib/systemd/system/vdsmd.service
[root@dell-r210ii-03 1.el7ev]# ls -l /lib/systemd/system/vdsmd.service 
-rw-r--r--. 1 root root 656 Mar 20 20:05 /lib/systemd/system/vdsmd.service

# systemctl status vdsmd
vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
   Active: failed (Result: start-limit) since Tue 2014-04-15 13:24:01 CEST; 1min 30s ago
  Process: 2831 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)

Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: vdsmd.service: control process exited, code=exited status=1
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Failed to start Virtual Desktop Server Manager.
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Unit vdsmd.service entered failed state.
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: vdsmd.service holdoff time over, scheduling restart.
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Stopping Virtual Desktop Server Manager...
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Starting Virtual Desktop Server Manager...
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: vdsmd.service start request repeated too quickly, refusing to start.
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Failed to start Virtual Desktop Server Manager.
Apr 15 13:24:01 dell-r210ii-03.rhev.lab.eng.brq.redhat.com systemd[1]: Unit vdsmd.service entered failed state.

Comment 12 errata-xmlrpc 2014-06-09 13:29:34 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-0504.html