Bug 1052082 - In the event of a full host power outage (including fence devices) a user must wait 19 mins (3 x 3 minute timeouts + 10 minutes for the transaction reaper) until they can manually fence a host to relocate guests.
Summary: In the event of a full host power outage (including fence devices) a user mus...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.3.1
Assignee: Eli Mesika
QA Contact: Tareq Alayan
URL:
Whiteboard: infra
Depends On: 1044091
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-13 09:49 UTC by rhev-integ
Modified: 2019-04-28 09:45 UTC (History)
14 users (show)

Fixed In Version: is34
Doc Type: Bug Fix
Doc Text:
Previously, it was not possible to relocate guests on a host if that host experienced complete power failure, including fence devices, until 19 minutes after the outage. This was caused by being forced to wait until three successive three-minute timeouts had elapsed and an additional 10 minutes for the transaction reappear. With this update, the method for determining whether a VDS action can be performed has been revised to allow execution of ClearNonResponsiveVdsVmsCommand while a host is in a reboot state, thereby shortening the time until virtual machines can be relocated.
Clone Of: 1044091
Environment:
Last Closed: 2014-03-03 13:31:19 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0227 0 normal SHIPPED_LIVE rhevm 3.3.1 bug fix update 2014-03-03 18:29:31 UTC
oVirt gerrit 23186 0 None None None Never

Comment 2 Tareq Alayan 2014-02-10 12:56:30 UTC 
couldn't reproduce. tested on  rhevm-3.3.1-0.47.el6ev.noarch
Comment 4 errata-xmlrpc 2014-03-03 13:31:19 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.

http://rhn.redhat.com/errata/RHBA-2014-0227.html
Note You need to log in before you can comment on or make changes to this bug.