Red Hat Bugzilla – Bug 1571755
Expand cluster notifications use integration id instead of cluster name
Last modified: 2018-09-04 03:06:23 EDT
Created attachment 1426604 [details] Events page with alerts Description of problem: Notifications related to the cluster expansion use `integration id` instead of `cluster short name` when the Cluster Name is set during import. These ids are in alerts and events. I have encountered this issue when nodes for expand were available: * `New nodes in cluster:integration_id` have node agents running now. Cluster is ready to expand.` * `New peers identified in cluster: integration_id. Make sure tendrl-ansible is executed for the new nodes so that expand cluster option can be triggered` * `Peer fbalak-usm2-gl6 in cluster cluster_id is Connected` Version-Release number of selected component (if applicable): glusterfs-3.12.2-8.el7rhgs.x86_64 tendrl-ansible-1.6.3-2.el7rhgs.noarch tendrl-api-1.6.3-1.el7rhgs.noarch tendrl-api-httpd-1.6.3-1.el7rhgs.noarch tendrl-commons-1.6.3-2.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-1.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-1.el7rhgs.noarch tendrl-node-agent-1.6.3-2.el7rhgs.noarch tendrl-notifier-1.6.3-2.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-1.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. Install tendrl. 2. Import cluster, during import set Cluster Name to `cluster1`. 3. Add peers to the cluster. 4. Install tendrl on new nodes via tendrl-ansible. 5. Check tendrl ui and initiate expand. 6. Check snmp, mail and ui for alerts. Actual results: In Events page for the cluster and in alerts are messages containing cluster id. Expected results: All messages should address the cluster by its cluster name `cluster1`. Additional info:
This issue is fixed
It seems that messages: * `New nodes in cluster:integration_id` have node agents running now. Cluster is ready to expand.` * `New peers identified in cluster: integration_id. Make sure tendrl-ansible is executed for the new nodes so that expand cluster option can be triggered` are fixed but message: * `Peer <host-id> in cluster <cluster-id> is Connected` is not fixed. --> ASSIGNED Tested with: glusterfs-3.12.2-10.el7rhgs.x86_64 tendrl-ansible-1.6.3-3.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-4.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch tendrl-node-agent-1.6.3-4.el7rhgs.noarch tendrl-notifier-1.6.3-2.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-1.el7rhgs.noarch
It is fixed. --> VERIFIED Tested with: tendrl-ansible-1.6.3-4.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-6.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-4.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-4.el7rhgs.noarch tendrl-node-agent-1.6.3-6.el7rhgs.noarch tendrl-notifier-1.6.3-3.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-3.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