This bug is about unfixed all expectations from bug 1515291. Description of problem: "systemctl reload" command doesn't reload gluster-integration configuration. Version-Release number of selected component (if applicable): tendrl-gluster-integration-1.5.4-3.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. get current date: $ date 2. get conf files for package: $ rpm -qc tendrl-gluster-integration 3. reload configuration: $ systemctl reload tendrl-gluster-integration 4. check if conf files from 2. are touched: $ find /etc/tendrl/ -type f | xargs stat | egrep '^Access: 2|File:' Actual results: "systemctl reload" doesn't reload service configuration. Expected results: "systemctl reload" reloads service configuration. Additional info: Cite from systemd documentation: reload PATTERN... Asks all units listed on the command line to reload their configuration. Note that this will reload the service-specific configuration, not the unit configuration file of systemd. If you want systemd to reload the configuration file of a unit, use the daemon-reload command. In other words: for the example case of Apache, this will reload Apache's httpd.conf in the web server, not the apache.service systemd unit file. This command should not be confused with the daemon-reload command.
Proopose to take this up in a later release. Moving to next release.
Fixed: https://github.com/Tendrl/gluster-integration/issues/491
Tested with: tendrl-gluster-integration-1.5.4-6.el7rhgs.noarch Configuration was not reloaded.
Tested with: tendrl-gluster-integration-1.5.4-8.el7rhgs.noarch Configuration was not reloaded.
Moving the bug out of 3.3.z