Bug 879719
| Summary: | power management: Fence Host fails if something went wrong in FenceQuietTimeBetweenOperationsInSec window [180seconds] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Chris Pelland <cpelland> |
| Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
| Status: | CLOSED ERRATA | QA Contact: | Tareq Alayan <talayan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.1.0 | CC: | aburden, bazulay, dyasny, emesika, hateya, iheim, lpeer, michal.skrivanek, mkenneth, oramraz, Rhev-m-bugs, talayan, yeylon, ykaul, yzaslavs |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt, infra | ||
| Fixed In Version: | si25 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if something went wrong in the FenceQuietTimeBetweenOperationsInSec window, the host would be unresponsive unless manually restarted. Now, FenceVdsBaseCommand no longer checks QuietTimeBetweenPmOperations if the command was invoked by the system and the host goes up as intended.
|
Story Points: | --- |
| Clone Of: | 871768 | Environment: | |
| Last Closed: | 2013-01-15 15:12:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 871768 | ||
| Bug Blocks: | |||
|
Description
Chris Pelland
2012-11-23 22:05:04 UTC
couldn't reproduce. The proxy has successfully fence the the non operational host in the 180 seconds window. And the host goes up. 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-2013-0003.html |