Bug 1571325 – Cluster remains listed by its short cluster name after unmanage

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1571325 - Cluster remains listed by its short cluster name after unmanage

Summary:	Cluster remains listed by its short cluster name after unmanage

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	web-admin-tendrl-commons (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	gowtham
QA Contact:	Filip Balák
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-04-24 10:09 EDT by Filip Balák
Modified:	2018-09-04 03:05 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-04 03:04:50 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	Tendrl/commons/issues/942	None	None	None	2018-04-26 01:06 EDT
Github	Tendrl/commons/pull/943	None	None	None	2018-04-25 09:49 EDT
Red Hat Product Errata	RHSA-2018:2616	None	None	None	2018-09-04 03:05 EDT

Groups: None (edit)

Description Filip Balák 2018-04-24 10:09:03 EDT

Description of problem:
The short cluster name remains on list of clusters after unmanage of cluster with specified short cluster name is completed. It changes only after next import.

Version-Release number of selected component (if applicable):
glusterfs-3.12.2-8.el7rhgs.x86_64
tendrl-ansible-1.6.3-2.el7rhgs.noarch
tendrl-api-1.6.3-1.el7rhgs.noarch
tendrl-api-httpd-1.6.3-1.el7rhgs.noarch
tendrl-commons-1.6.3-2.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-1.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-1.el7rhgs.noarch
tendrl-node-agent-1.6.3-2.el7rhgs.noarch
tendrl-notifier-1.6.3-2.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-1.el7rhgs.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install tendrl.
2. Import cluster, set `Cluster Name` to `cluster1` in import cluster wizard.
3. Unmanage the cluster.
4. Go to list of all clusters.

Actual results:
On cluster list is the cluster listed as `cluster1`.

Expected results:
The cluster should be listed by its `integration id`.

Additional info:

Comment 3 Filip Balák 2018-05-10 04:10:57 EDT

Seems ok --> VERIFIED

Tested with:
tendrl-ansible-1.6.3-3.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-4.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch
tendrl-node-agent-1.6.3-4.el7rhgs.noarch
tendrl-notifier-1.6.3-2.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-1.el7rhgs.noarch
ansible-2.5.2-1.el7ae.noarch

Comment 5 errata-xmlrpc 2018-09-04 03:04:50 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.