Bug 1526338

Summary:	[RFE] Enhance unmanage cluster workflow to remove only specified (affected) cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nishanth Thomas <nthomas>
Component:	web-admin-tendrl-node-agent	Assignee:	Shubhendu Tripathi <shtripat>
Status:	CLOSED ERRATA	QA Contact:	Filip Balák <fbalak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	asriram, fbalak, mbukatov, nthomas, rcyriac, rghatvis, rhs-bugs, shtripat, srmukher
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 07:00:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1564107, 1570048, 1571280
Bug Blocks:	1503132

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