Created attachment 1476098 [details] events page Description of problem: Currently there are alerts and event messages: ``` Service: glustershd is connected in cluster <cluster> Service: glustershd is disconnected in cluster <cluster> ``` It is not clear from these messages what nodes are affected. Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-6.el7rhgs.noarch tendrl-api-1.6.3-5.el7rhgs.noarch tendrl-api-httpd-1.6.3-5.el7rhgs.noarch tendrl-commons-1.6.3-12.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-10.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-10.el7rhgs.noarch tendrl-node-agent-1.6.3-10.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-10.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. Import cluster with distributed replicated volume. 2. Connect to one of the volume nodes and get pid of glustershd process: $ cat /var/run/gluster/glustershd/glustershd.pid <glustershd-pid> 3. kill <glustershd-pid> 4. Wait for alert in UI. 5. restart glusterd service on node with killed glustershd. This should start glustershd. Actual results: Events and alerts Service: glustershd is disconnected in cluster <cluster> Service: glustershd is connected in cluster <cluster> are generated. Expected results: There should be mention of node in alert because user now doesn't know what nodes or how many are affected. Additional info:
PR is under review: https://github.com/Tendrl/gluster-integration/pull/695
I have modified alert message formate for SVC related alerts like Service: {service_nmae} is Connected/Disconnected on node {peer_hostname/ip} of cluster {cluster_short_name}
QE team will test this bug as noted in the description.
https://github.com/Tendrl/gluster-integration/pull/695
fixed in tendrl-gluster-integration-1.6.3-10.el7rhgs
All acks provided, attaching to the tracker.
Messages look like Gowtham described in comment 3. --> VERIFIED Tested with: tendrl-ansible-1.6.3-7.el7rhgs.noarch tendrl-api-1.6.3-5.el7rhgs.noarch tendrl-api-httpd-1.6.3-5.el7rhgs.noarch tendrl-commons-1.6.3-12.el7rhgs.noarch tendrl-gluster-integration-1.6.3-10.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-10.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-10.el7rhgs.noarch tendrl-node-agent-1.6.3-10.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-11.el7rhgs.noarch
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/RHSA-2018:2616