Bug 1516135 - When import fails, the import button should be accessible only after unmanage
Summary: When import fails, the import button should be accessible only after unmanage
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-node-agent
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Neha Gupta
QA Contact: Filip Balák
Depends On: 1514442 1564107
Blocks: 1502877 1503134
TreeView+ depends on / blocked
Reported: 2017-11-22 07:02 UTC by Rochelle
Modified: 2021-12-10 15:25 UTC (History)
11 users (show)

Fixed In Version: tendrl-ui-1.6.3-4.el7rhgs
Doc Type: Bug Fix
Doc Text:
Previously, there was no way to unmanage a cluster which was partially imported due to tendrl-gluster-integration install failure on few nodes of the cluster. Despite the unsuccessful import, the cluster displayed status as being successfully imported and managed by Web Administration. This depiction of the cluster in the Web Administration interface was not correct as not all the peers of the cluster were well imported and reported in the interface. With this fix, now an import job would be marked as finished only if all the peers report tendrl-gluster-integration running on them and their first round of synchronization of data is done in the Web Administration environment. With the unmanage cluster functionality in place, any affected cluster can be unmanaged and the underlying issues can be fixed before re-importing the cluster in Web Administration environment. If import fails, the issues can be corrected in the underlying cluster and re-imported in the Web Administration environment.
Clone Of:
Last Closed: 2018-09-04 06:58:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
When import fails, the import button should be accessible (81.39 KB, image/png)
2017-11-22 07:02 UTC, Rochelle
no flags Details
screenshot 1 (it's possible to run both import and unmanage) (86.91 KB, image/png)
2018-05-31 16:14 UTC, Martin Bukatovic
no flags Details
screenshot 2 (it's possible to run both import, but with a warning) (132.57 KB, image/png)
2018-05-31 16:15 UTC, Martin Bukatovic
no flags Details

System ID Private Priority Status Summary Last Updated
Github Tendrl node-agent issues 662 0 None closed When cluster import task fails and the cluster is shown as ok in Tendrl UI, the problem is not reported anywhere else or... 2020-06-08 15:49:19 UTC
Red Hat Bugzilla 1516211 0 unspecified CLOSED describe in detail what to do when ImportCluster task fails 2021-02-22 00:41:40 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 Bugzilla 1615418 0 unspecified CLOSED Import cluster job can be created via API right after previous import failed 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 06:59:57 UTC

Internal Links: 1516211 1526338 1615418

Description Rochelle 2017-11-22 07:02:51 UTC
Created attachment 1357259 [details]
When import fails, the import button should be accessible

Description of problem:
When the cluster import fails, the import option that has been provided, is not enabled for re-importing the cluster (after fixing the issue) 

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

How reproducible:

Actual results:
Re-importing the cluster is not enabled

Expected results:
Re-importing the cluster should be enabled

Comment 2 Martin Bukatovic 2017-11-22 09:12:50 UTC
This is part of larger problem which is being discussed in upstream here:


Comment 4 Martin Bukatovic 2017-11-22 09:19:08 UTC
Status of downstream build wrt upstream issue Tendrl/node-agent/issues/662, when
I reproduce this issue, I see that:

* ImportCluster task is shown as failed in Tasks page and Tasks Details page
  (as expected, and as previously observed in upstream)
* Cluster is marked with question mark icon, with "import failed" message shown
  for it, without an option to run the import again (import button is disabled)

[root@usm1-gl1 ~]# rpm -qa | grep tendrl | sort                                 
[root@usm1-gl1 ~]# rpm -qa | grep gluster | sort                                

Comment 5 Martin Bukatovic 2017-11-22 09:23:37 UTC
Moving component to node-agent, as ui can't show import button when the feature
is not present on purpose in the backend.

Comment 6 Rohan Kanade 2017-11-22 09:25:11 UTC
Tendrl will not allow retries for failed import. Users will need to re-install Tendrl and try import again. Although Tendrl does intend to support this use-case in a future release

More details on uninstall: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.4-(install-guide)#uninstall-tendrl

Comment 10 Filip Balák 2018-05-21 09:42:05 UTC
* According to the specification (https://github.com/Tendrl/specifications/pull/255/files#diff-c5716c66b1f0e774bbfca74a2aa0b980R124) there should be triggered unmanage after import fails (automatically?). But there is currently triggered only Import again.
* In Import wizard is message:
`Import cluster previously failed with <job-id>. Be sure that all the issues have been corrected and the cluster has been unmanaged before proceeding.` which indicates that unmanage should be triggered by user.
* When unmanage fails the `Import` button on cluster list is inaccessible.

Is this expected behaviour?

Tested with:

Comment 11 Shubhendu Tripathi 2018-05-21 12:22:11 UTC
Filip, currently its like that. If import fails, user needs to clean the errors on underlying storage nodes and then import the cluster back again.
When un-manage fails the un-manage should be allowed again for the cluster.

Comment 14 Martin Bukatovic 2018-05-31 16:14:26 UTC
Created attachment 1446327 [details]
screenshot 1 (it's possible to run both import and unmanage)

Comment 15 Martin Bukatovic 2018-05-31 16:15:07 UTC
Created attachment 1446328 [details]
screenshot 2 (it's possible to run both import, but with a warning)

Comment 17 Nishanth Thomas 2018-06-06 06:12:33 UTC
Ack. This looks good

Comment 19 Martin Bukatovic 2018-06-29 18:03:27 UTC
Retrying with:


Performing scenario described in comment 16:

 * create a problem which makes import fail
 * run import
 * wait for the import to fail (breaking WA repourl on one storage machine)
 * checking that it's not possible to run import immediately again
 * fixing the problem (introduced in the 1st step)
 * run unmanage
 * run import
 * check that cluster is imported with success

But the unmanage failed, so I can't verify this. Will report and update
related BZs.

Until we can run unmanage in such easy scenario, we can't verify this BZ.

Comment 20 Martin Bukatovic 2018-06-29 19:32:54 UTC
During failed verification of this BZ, I reported:

 * bz 1596839
 * bz 1596820

and still have to debug and either report or update BZ for the failure of
cluster unamanage.

Comment 21 Filip Balák 2018-08-13 14:44:09 UTC
Scenario from Comment 16 works as expected. User can initiate cluster import via API after previous import failed and cluster was not unmanaged (BZ 1615418) but this BZ is about import button which is not available during that scenario. --> VERIFIED

Tested with:

Comment 24 Shubhendu Tripathi 2018-09-04 02:53:24 UTC
The doc-text looks good

Comment 26 errata-xmlrpc 2018-09-04 06:58:45 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.


Note You need to log in before you can comment on or make changes to this bug.