Description of problem: While attempting to remove a host that is in Maintenance, the following error occurs: "Cannot remove Host. Related operation is already in progress." Note: This does not happen on every remove attempt, and subsequent attempts to move are typically successful. Version-Release number of selected component (if applicable): bb6 How reproducible: Steps to Reproduce: 1. Add host and move it to Up status. 2. Move host to Maintenance 3. Remove host Actual results: Unable to remove host that is in maintenance. Expected results: Once host is in Maintenance state, should be able to remove the host. Additional info:
Created attachment 777334 [details] Screen Shot
Created attachment 786170 [details] Log file Bug encountered during automated overnight run.
This can not be permanently fixed. Only the interval of polling can be increased to avoid the locking probability to a large extent. But that would have some GUI refresh not happening for that interval. We will try to increase it from 5 sec to 30 sec and see.
I'm not sure if increasing the polling interval is the right way to fix this. This would result in other issues like volume status/new volumes/ new bricks are not synced in engine immediately. Can the automation tests be changed to introduce a delay before 2 operations?
Sent patch to upstream: http://gerrit.ovirt.org/#/c/21865
Added proper locking mechanism for backend (gluster command) execution to handle this situation.
Verified in cb12.
Please review the edited DocText.
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. http://rhn.redhat.com/errata/RHEA-2014-0208.html
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days