Red Hat Bugzilla – Bug 1559368
The expand cluster flow for cluster should be user initiated and not automatic
Last modified: 2018-09-04 03:02:57 EDT
Description of problem: Currently when new nodes are peer probed in cluster automatically an expansion is triggered in backend and if tendrl-node-agent is not installed and started well within time the expansion job used to mostly timed out. Rather the expansion of cluster should be user triggered based on new nodes notified in the UI. Version-Release number of selected component (if applicable): How reproducible: Most of the cases if tendrl-node-agent doesnt get installed and started on additional nodes well within time Steps to Reproduce: 1. Create a 2 node gluster cluster 2. Import the cluster in tendrl 3. Peer probe two additional nodes to the gluster cluster from CLI 4. Wait for say 30 mins and then install and start tendrl-node-agent on additional nodes 5. Check the expand cluster job on UI Actual results: The job is timed out Expected results: The expand job should be possible to trigger from UI. Once peers are added to the cluster from CLI UI should notify about the new peers found in the cluster. Once user runs tendrl-ansible for the new nodes and node-agent the UI should mark the cluster as expand pending. At this stage user should be able to trigger expansion from UI and it should be successful. Additional info:
This will be verified during feature testing of expand cluster.
Looks ok. --> 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-5.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-3.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-3.el7rhgs.noarch tendrl-node-agent-1.6.3-5.el7rhgs.noarch tendrl-notifier-1.6.3-3.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-2.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