Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685055 - Cluster is stuck in Unmanaging Cluster state
Summary: Cluster is stuck in Unmanaging Cluster state
Keywords:
Status: NEW
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-ui
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Neha Gupta
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 09:26 UTC by Elena Bondarenko
Modified: 2019-03-13 11:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
Screenshot of "No Task Detail Found Detected" message (deleted)
2019-03-04 09:26 UTC, Elena Bondarenko
no flags Details
Unmanage job log in UI (deleted)
2019-03-08 14:28 UTC, Elena Bondarenko
no flags Details

Description Elena Bondarenko 2019-03-04 09:26:31 UTC
Created attachment 1540571 [details]
Screenshot of "No Task Detail Found Detected" message

Description of problem:
On Friday the last thing I did to my cluster was run cluster unmanage. On Monday morning UI shows the cluster as if it's still running Unmanage, but clicking on View Details of the unmanaging task leads to a page with error message "No Task Detail Found Detected".
The cluster is stuck in this state, so it's impossible to properly unmanage it or import it again.


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

tendrl-ui-1.6.3-15.el7rhgs.noarch


How reproducible:

I'll try to reproduce it next weekend


Steps to Reproduce:
1. Import and then unmanage cluster
2. Leave it for 2,5 days
3. Log in to UI again


Actual results:

Cluster is stuck in Unmanaging Cluster state, so it's impossible to import it.


Expected results:

Cluster is always in a state that can be changed so that import becomes possible.

Comment 2 Elena Bondarenko 2019-03-08 14:24:45 UTC
Today Unmanage job on my cluster got stuck in a very similar way: it started running, didn't produce any errors and its status is still Processing. It's been 40 minutes since this job was started. Ten minutes after the job was started an alert appeared in UI: Cluster gluster-0f5c443368637cb718eaa60465d480d31fa04c0042e5d606102ac04c3d9a4ac8 moved to unhealthy state.

Comment 3 Elena Bondarenko 2019-03-08 14:28:07 UTC
Created attachment 1542118 [details]
Unmanage job log in UI

Comment 4 Elena Bondarenko 2019-03-13 11:17:16 UTC
Today UnmanageCluster task got stuck again after some rounds of Import-Unmanage-Import-Unmanage.
There's an error message in the task log "Could not find atom tendrl.objects.Cluster.atoms.StopMonitoringServices", but the task's status is still Processing, not Failed even after 20 minutes of not actually doing anything.


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