Bug 1526338 - [RFE] Enhance unmanage cluster workflow to remove only specified (affected) cluster
Summary: [RFE] Enhance unmanage cluster workflow to remove only specified (affected) c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-node-agent
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Shubhendu Tripathi
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On: 1564107 1570048 1571280
Blocks: 1503132
TreeView+ depends on / blocked
 
Reported: 2017-12-15 09:18 UTC by Nishanth Thomas
Modified: 2018-09-04 07:01 UTC (History)
9 users (show)

Fixed In Version: tendrl-ansible-1.6.1-2.el7rhgs.noarch.rpm, tendrl-api-1.6.1-1.el7rhgs.noarch.rpm, tendrl-commons-1.6.1-1.el7rhgs.noarch.rpm, tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch.rpm, tendrl-node-agent-1.6.1-1.el7, tendrl-ui-1.6.1-1.el7rhgs.noarch.rpm,
Doc Type: Known Issue
Doc Text:
Previously, unmanaging an affected individual cluster caused other clusters managed by Web Administration to be unmanaged. With this fix, unmanaging the affected cluster will have no impact on the other clusters being managed by Web Administration.
Clone Of:
Environment:
Last Closed: 2018-09-04 07:00:31 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/Tendrl commons issues 797 0 None None None 2020-07-02 04:06:21 UTC
Red Hat Bugzilla 1516135 0 unspecified CLOSED When import fails, the import button should be accessible only after unmanage 2021-12-10 15:25:43 UTC
Red Hat Bugzilla 1559387 0 unspecified CLOSED Back to back import and unmanage cluster multiple time resuts in a situation where import is complete but not marked cor... 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1565734 0 unspecified CLOSED Disk utilization and carbon data archiving behaviour 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1565978 1 None None None 2024-09-18 00:47:37 UTC
Red Hat Bugzilla 1571906 1 None None None 2024-09-18 00:47:46 UTC
Red Hat Bugzilla 1584095 0 unspecified CLOSED Unmanage fails after failed import 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:01:24 UTC


Description Nishanth Thomas 2017-12-15 09:18:49 UTC 
Description of problem:

If Cluster import fails or an existing cluster need to be expanded with additional hosts, current procedure results in removal of all the managed clusters.

Expected results:

This procedure should remove only the affected cluster
Comment 4 Martin Bukatovic 2018-04-04 11:34:55 UTC 
This is basically RFE BZ for unmanage feature, as described in upstream here:

https://github.com/Tendrl/specifications/pull/255

Correct?
Comment 5 Nishanth Thomas 2018-04-06 08:21:58 UTC 
yes
Comment 8 Nishanth Thomas 2018-05-03 06:03:53 UTC 
 BZ 1564107 already verified
Comment 9 Filip Balák 2018-06-25 11:15:35 UTC 
Basic workflow for unmanaging cluster works. It works for positive testcases and also for unmanage after failure of import (BZ 1570048, BZ 1564107). When the cluster is unmanaged, all other clusters remain as managed if they are already managed.
--> VERIFIED

Tested with:
tendrl-ansible-1.6.3-5.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-7.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-5.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch
tendrl-node-agent-1.6.3-7.el7rhgs.noarch
tendrl-notifier-1.6.3-4.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-4.el7rhgs.noarch
Comment 14 errata-xmlrpc 2018-09-04 07:00:31 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.