Bug 1561323

Summary:	[RFE] tcmu-runner: introduce the dynamic reloading config feature support
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Xiubo Li <xiubli>
Component:	tcmu-runner	Assignee:	Xiubo Li <xiubli>
Status:	CLOSED ERRATA	QA Contact:	Rachael <rgeorge>
Severity:	high	Docs Contact:
Priority:	high
Version:	cns-3.9	CC:	akrishna, atumball, mchristi, pkarampu, pprakash, prasanna.kalever, rgeorge, rhs-bugs, xiubli
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	OCS 3.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcmu-runner-1.2.0-25.el7rhgs	Doc Type:	Enhancement
Doc Text:	Updates to the tcmu-runner configuration file are now applied automatically, removing the need to restart the tcmu-runner daemon when any configuration changes are made.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-24 04:52:58 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:	1632821

Description Xiubo Li 2018-03-28 06:08:43 UTC

Description of problem:

For now if we want to change the configuration of the tcmu-runner daemon, we have to reboot the tcmu-runner daemon after that to make it work.

After the dynamic reloading config feature is support, no reboot is needed any more.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Xiubo Li 2018-03-28 06:11:27 UTC

The upstream patches are here: https://github.com/open-iscsi/tcmu-runner/pull/176

Comment 17 Anjana KD 2018-10-11 07:01:23 UTC

Updated the Doc text field. Kindly review

Comment 19 Anjana KD 2018-10-12 06:10:15 UTC

updated the changes.

Comment 21 errata-xmlrpc 2018-10-24 04:52:58 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:2987