Bug 1515291

Summary:	systemctl reload kills gluster integration daemon
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Martin Kudlej <mkudlej>
Component:	web-admin-tendrl-gluster-integration	Assignee:	Nishanth Thomas <nthomas>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	bmekala, ppenicka, rhs-bugs, rkanade, sanandpa, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tendrl-gluster-integration-1.5.4-4.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-18 04:37:36 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 Martin Kudlej 2017-11-20 14:09:12 UTC

Description of problem:
Configuration reloading of gluster integration daemon kills it.

Version-Release number of selected component (if applicable):
tendrl-gluster-integration-1.5.4-3.el7rhgs.noarch

How reproducible:
100%

Steps to Reproduce:
1. daemon is running - systemctl status tendrl-gluster-integration
2. reload configuration - systemctl reload tendrl-gluster-integration
3. daemon is down - systemctl status tendrl-gluster-integration

Actual results:
Configuration reloading of gluster integration daemon kills it.

Expected results:
Configuration reloading of gluster integration daemon will reload daemon configuration:
/usr/share/tendrl/gluster-integration/gluster-integration.conf.yaml

Comment 2 Rohan Kanade 2017-11-21 05:47:56 UTC

systemctl reload is used for reloading configurations for the service.

Fixed: https://github.com/Tendrl/gluster-integration/issues/491

Comment 4 Petr Penicka 2017-11-21 12:10:09 UTC

Giving all acks for 3.3.1 after call confirming this fix is going into today's build.

Comment 9 errata-xmlrpc 2017-12-18 04:37:36 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-2017:3478