Bug 1525097 - tendrl-notifier doesn't reload configuration
Summary: tendrl-notifier doesn't reload configuration
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-notifier
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On: 1515276
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-12 15:35 UTC by Rochelle
Modified: 2019-05-08 20:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
When the user runs the systemctl reload command, it returns an error. In addition, the tendrl notifier configuration does not reload. Workaround: Run systemctl restart command of tendrl-notifier service and the configuration will be reloaded.
Clone Of:
Environment:
Last Closed: 2019-05-08 20:10:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Rochelle 2017-12-12 15:35:10 UTC
Description of problem:
========================
After changing the notifier.conf.yaml file, the logs don't capture the new configuration.


Version-Release number of selected component (if applicable):
=============================================================
tendrl-api-1.5.4-4.el7rhgs.noarch
tendrl-grafana-plugins-1.5.4-14.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-node-agent-1.5.4-16.el7rhgs.noarch
tendrl-ansible-1.5.4-7.el7rhgs.noarch
tendrl-commons-1.5.4-9.el7rhgs.noarch
tendrl-ui-1.5.4-6.el7rhgs.noarch
tendrl-monitoring-integration-1.5.4-14.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-api-httpd-1.5.4-4.el7rhgs.noarch
tendrl-notifier-1.5.4-6.el7rhgs.noarch



Steps to Reproduce:
==================
1. change some configuration variable in notifier configuration file
2. systemctl reload tendrl-notifier
3. check in output of "find /etc/tendrl/ -type f | xargs stat | grep '^Access: 2'" that notifier has read configuration
4. check logs that notifier used new value of configured option



Actual results:
================
The logs don't capture the change

Expected results:
=================
The logs should capture the change

Comment 6 Nishanth Thomas 2017-12-15 12:27:16 UTC
Updated, pls check


Note You need to log in before you can comment on or make changes to this bug.