Bug 1308418

Summary:	VDSMD service should be disabled by default after installation on RHEL7
Product:	[oVirt] vdsm	Reporter:	Sahina Bose <sabose>
Component:	Core	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED WONTFIX	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.17.18	CC:	bugs, mmalhotr, nlevinki, olim, oourfali, pstehlik, rhs-bugs, rhsc-qe-bugs, sabose, sankarshan, shtripat, ybronhei
Target Milestone:	---	Flags:	sabose: ovirt-3.6.z? rule-engine: planning_ack? rule-engine: devel_ack? pstehlik: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1305201	Environment:
Last Closed:	2016-03-17 07:13:03 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:

Description Sahina Bose 2016-02-15 07:12:00 UTC

Description of problem:

vdsm service on RHEL 7 is enabled by default on installation. When the server is rebooted, there are errors related to being unable to start the service as vdsm has not been configured. (The node has not been added to oVirt)

Note: vdsm on RHEL 6 is disabled by default and works as expected

Comment 3 Yaniv Bronhaim 2016-02-24 13:57:05 UTC

we currently enable vdsmd.service supervdsmd.service vdsm-network.service and mom-vdsm.service as part of vdsm rpm installation.

host-deploy enables vdsmd and supervdsmd.

and as far as I see - we do chkconfig on for vdsmd and supervdsmd over el6.. what vdsm versions do you use? the behavior should be the same

Comment 4 Oved Ourfali 2016-03-08 08:33:38 UTC

Sahina?

Comment 5 Sahina Bose 2016-03-16 10:12:42 UTC

vdsm version was 4.16.30

Comment 7 Sahina Bose 2016-03-16 10:17:31 UTC

The behaviour is consistent upstream for EL6 and EL7 , sorry about the confusion.

You can close this if this is the intended behaviour of vdsm/supervdsm.

Comment 8 Yaniv Bronhaim 2016-03-17 07:13:03 UTC

Yes, this is the intend behavior in both distributions and I don't see any problem with that ... unless someone has good reason for keeping it disabled after yum installation, please re-open.