Bug 1052082
| Summary: | 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. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
| Status: | CLOSED ERRATA | QA Contact: | Tareq Alayan <talayan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.2.0 | CC: | acathrow, adahms, bazulay, emesika, flo_bugzilla, iheim, jentrena, lpeer, lyarwood, mgrac, pstehlik, Rhev-m-bugs, sputhenp, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | infra | ||
| 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.
|
Story Points: | --- |
| Clone Of: | 1044091 | Environment: | |
| Last Closed: | 2014-03-03 13:31:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1044091 | ||
| Bug Blocks: | |||
|
Comment 2
Tareq Alayan
2014-02-10 12:56:30 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 |