Bug 1559368 - The expand cluster flow for cluster should be user initiated and not automatic
Summary: The expand cluster flow for cluster should be user initiated and not automatic
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-node-agent
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Shubhendu Tripathi
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On:
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-03-22 12:14 UTC by Shubhendu Tripathi
Modified: 2018-09-04 07:02 UTC (History)
5 users (show)

Fixed In Version: tendrl-commons-1.6.1-3.el7rhgs, tendrl-api-1.6.1-3.el7rhgs, tendrl-ui-1.6.1-3.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 07:01:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/Tendrl api issues 385 0 None None None 2018-03-27 06:55:49 UTC
Github https://github.com/Tendrl api issues 400 0 None None None 2018-03-27 06:56:13 UTC
Github https://github.com/Tendrl commons issues 869 0 None None None 2018-03-27 06:52:51 UTC
Github https://github.com/Tendrl commons issues 875 0 None None None 2018-03-27 06:52:29 UTC
Github https://github.com/Tendrl ui issues 888 0 None None None 2018-03-27 06:57:00 UTC
Red Hat Bugzilla 1516417 0 unspecified CLOSED Expanding an existing RHGS cluster managed by RHGS WA by adding nodes and monitoring 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:02:56 UTC

Internal Links: 1516417

Description Shubhendu Tripathi 2018-03-22 12:14:58 UTC 
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:
Comment 2 Martin Bukatovic 2018-03-28 09:49:33 UTC 
This will be verified during feature testing of expand cluster.
Comment 7 Filip Balák 2018-05-23 10:29:27 UTC 
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
Comment 9 errata-xmlrpc 2018-09-04 07:01:53 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.