Bug 1564107

Summary: un-manage task managed cluster check
Product: Red Hat Gluster Storage Reporter: Lubos Trilety <ltrilety>
Component: web-admin-tendrl-uiAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: sds-qe-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: mbukatov, nthomas, rhs-bugs, shtripat
Target Milestone: ---Keywords: TestBlocker
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: tendrl-commons-1.6.3-2.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 07:03:46 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:
Bug Depends On:    
Bug Blocks: 1503137, 1516135, 1526338    

Description Lubos Trilety 2018-04-05 11:55:53 UTC
Description of problem:
Un-manage fails when the tendrl.objects.Cluster.atoms.IsClusterManaged check says:
Failed pre-run: tendrl.objects.Cluster.atoms.IsClusterManaged for flow: Unmanage a Gluster Cluster

There's something broken in the check as it states the cluster to be managed even when import for some reason failed however tendrl-gluster-integration packages were installed on some/all nodes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Import cluster and un-manage cluster first time
2. Remove tendrl-gluster-integration package from some gluster server node. Flaw a tendrl repository, e.g. change baseurl link to some which does not exist.
3. Re-import again
4. Try to un-manage the cluster
(The scenario could be reproduced without the first step, however in such case it doesn't always happen)

Another scenario:
1. Try to import a running gluster cluster for which a newer gluster packages are available.
2. Try to un-manage the cluster

Actual results:
Un-manage fails:
Failed pre-run: tendrl.objects.Cluster.atoms.IsClusterManaged for flow: Unmanage a Gluster Cluster

Expected results:
Un-manage could be done without an issue.

Additional info:

Comment 1 Lubos Trilety 2018-04-06 09:48:35 UTC
The wrong of the tendrl.objects.Cluster.atoms.IsClusterManaged check is probably elsewhere. It seems to say the cluster is not managed, which is true and correct. However it should not fail the whole un-manage task as the task should run for a cluster which failed to be imported.

That said the first scenario does not need the first step at all.

Comment 8 Lubos Trilety 2018-04-24 12:01:27 UTC
Verified in:

The problematic check is not there anymore.

Comment 10 errata-xmlrpc 2018-09-04 07:03:46 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.