Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1526338 - [RFE] Enhance unmanage cluster workflow to remove only specified (affected) cluster
[RFE] Enhance unmanage cluster workflow to remove only specified (affected) c...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-node-agent (Show other bugs)
3.3
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: Shubhendu Tripathi
Filip Balák
: FutureFeature
Depends On: 1564107 1570048 1571280
Blocks: 1503132
  Show dependency treegraph
 
Reported: 2017-12-15 04:18 EST by Nishanth Thomas
Modified: 2018-09-04 03:01 EDT (History)
9 users (show)

See Also:
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 03:00:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github https://github.com/Tendrl/commons/issues/797 None None None 2018-01-12 01:46 EST
Red Hat Product Errata RHSA-2018:2616 None None None 2018-09-04 03:01 EDT

  None (edit)
Description Nishanth Thomas 2017-12-15 04:18:49 EST
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 07:34:55 EDT
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 04:21:58 EDT
yes
Comment 8 Nishanth Thomas 2018-05-03 02:03:53 EDT
 BZ 1564107 already verified
Comment 9 Filip Balák 2018-06-25 07:15:35 EDT
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 03:00:31 EDT
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.