Bug 1459110 - Expand/Shrink cluster doesn't work for RHCS
Summary: Expand/Shrink cluster doesn't work for RHCS
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: Dashboard
Version: 3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3
Assignee: Ankush Behl
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-06 10:32 UTC by Filip Balák
Modified: 2018-11-19 05:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:42:04 UTC
Embargoed:


Attachments (Terms of Use)
List of clusters image (45.12 KB, image/png)
2017-06-06 10:32 UTC, Filip Balák
no flags Details

Description Filip Balák 2017-06-06 10:32:27 UTC
Created attachment 1285332 [details]
List of clusters image

Description of problem:
On right side of each cluster listed in list of clusters is button with options to Expand, Shrink and Unmanage. These options are grey and unavailable.

Version-Release number of selected component (if applicable):
tendrl-alerting-3.0-alpha.2.el7scon.noarch
tendrl-api-3.0-alpha.3.el7scon.noarch
tendrl-api-doc-3.0-alpha.3.el7scon.noarch
tendrl-api-httpd-3.0-alpha.3.el7scon.noarch
tendrl-commons-3.0-alpha.7.el7scon.noarch
tendrl-dashboard-3.0-alpha.3.el7scon.noarch
tendrl-node-agent-3.0-alpha.7.el7scon.noarch
tendrl-performance-monitoring-3.0-alpha.4.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Import or Create cluster
2. Open cluster list in dashboard (Clusters button in left panel)
3. Click on button with 3 dots in right part of the listed cluster.
4. Try to click on some options from the popup.

Actual results:
Options for Expand/Shrink are doing nothing.

Expected results:
Options for Expand/Shrink should lead to form where these operations can be managed

Additional info:

Comment 4 Shubhendu Tripathi 2018-11-19 05:42:04 UTC
This product is EOL now


Note You need to log in before you can comment on or make changes to this bug.