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

Bug 1063886

Summary:	'vdsm-tool configure --force' does not configure sanlock sometimes
Product:	[Retired] oVirt	Reporter:	Yedidyah Bar David <didi>
Component:	vdsm	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	abaron, acathrow, bazulay, danken, gklein, iheim, mgoldboi, sbonazzo, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-12 08:53:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2014-02-11 15:24:20 UTC

Description of problem:

Under some circumstances, 'vdsm-tool configure --force' does not add sanlock to kvm/qemu groups and 'service vdsmd start' then fails.

Version-Release number of selected component (if applicable):

4.14.1-3.el6.x86_64

How reproducible:

Always?

Steps to Reproduce:
0. not sure what - probably 'vdsm-tool configure --force', starting some services
1. initctl stop libvirtd
2. service sanlock stop
3. service wdmd stop
4. remove sanlock from qemu and kvm groups in /etc/group
5. vdsm-tool configure --force
6. service vdsmd start

Actual results:

vdsmd start fails

Expected results:

should succeed

Additional info:

If after 'vdsmd start' I run again 'vdsm-tool configure --force', it correctly adds sanlock to these groups and then 'service vdsmd start' succeeds.

The actual flow was a failed attempt to install all-in-one on a clean centos machine, due to bug #1063869 , and a later attempt with a fix to that bug failed for the current bug (or so it seems based on the logs). I later reproduced using the steps above, not sure if they are applicable to a clean system.

Comment 1 Yaniv Bronhaim 2014-02-12 08:53:41 UTC


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