Bug 1585200

Summary:	runner: don't allow multiple instances of daemon to run
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prasanna Kumar Kalever <prasanna.kalever>
Component:	tcmu-runner	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED ERRATA	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	cns-3.10	CC:	bgoyal, kramdoss, nberry, pkarampu, prasanna.kalever, rhs-bugs, rtalur, sankarshan, vbellur, xiubli
Target Milestone:	---
Target Release:	CNS 3.10
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcmu-runner-1.2.0-20.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-12 09:25:34 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:
Bug Depends On:
Bug Blocks:	1568862

Description Prasanna Kumar Kalever 2018-06-01 13:38:30 UTC

Description of problem:

In tcmu-runner, until now there is no check to defend on multiple runs of daemon within the same node.

So there is a possibility of two or more runner instances running on the same node at a given time.


PR:
https://github.com/open-iscsi/tcmu-runner/pull/418

The patch fixing takes a non blocking lock on 'tcmu.lock' file, if it succeeds only then daemon is allowed to run, if there is already a lock on lock-file (taken by some other instance of tcmu-runner) we will exit.

Comment 12 errata-xmlrpc 2018-09-12 09:25: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.

https://access.redhat.com/errata/RHEA-2018:2691