Bug 1584095 - Unmanage fails after failed import
Summary: Unmanage fails after failed import
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-node-agent
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.4.0
Assignee: Anmol Sachan
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On: 1589729
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-05-30 09:27 UTC by Filip Balák
Modified: 2018-09-04 07:08 UTC (History)
6 users (show)

Fixed In Version: tendrl-commons-1.6.3-9.el7rhgs.noarch
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 07:07:10 UTC
Embargoed:


Attachments (Terms of Use)
Failed unmanage task (112.65 KB, image/png)
2018-05-30 09:27 UTC, Filip Balák
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github Tendrl commons issues 1019 0 None None None 2018-07-03 08:28:14 UTC
Red Hat Bugzilla 1526338 0 unspecified CLOSED [RFE] Enhance unmanage cluster workflow to remove only specified (affected) cluster 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:08:05 UTC

Internal Links: 1526338

Description Filip Balák 2018-05-30 09:27:12 UTC
Created attachment 1445736 [details]
Failed unmanage task

Description of problem:
When one or more nodes are shut down cluster import is triggered, the import fails. The unmanage task fails also even after nodes are started again.

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

How reproducible:
90%

Steps to Reproduce:
1. Prepare cluster to import into WA.
2. Shut down one or more nodes.
3. Import the cluster. Import times out.
4. Start nodes.
5. Unmanage the cluster.

Actual results:
The unmanage task almost always fails.

Expected results:
Unmanage should work in this scenario.

Additional info:

Comment 9 Filip Balák 2018-07-26 11:46:10 UTC
This is no longer reproducible in current version. --> VERIFIED

Tested with:
tendrl-ansible-1.6.3-5.el7rhgs.noarch
tendrl-api-1.6.3-4.el7rhgs.noarch
tendrl-api-httpd-1.6.3-4.el7rhgs.noarch
tendrl-commons-1.6.3-9.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-7.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch
tendrl-node-agent-1.6.3-9.el7rhgs.noarch
tendrl-notifier-1.6.3-4.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-8.el7rhgs.noarch

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