Bug 1074578
| Summary: | VM split brain caused by network outage | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Roy Golan <rgolan> |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.3.0 | CC: | acathrow, eedri, iheim, lbopf, lpeer, mavital, michal.skrivanek, ofrenkel, rgolan, Rhev-m-bugs, rhodain, sherold, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the GetVmStats request would fail. When this happened, a high-availability virtual machine was listed as 'down', and was rescheduled again on a different host, causing two instances of the same virtual machine to be running at once. Now, the system will ignore virtual machine updates until the next monitoring cycle, allowing the system to retrieve the virtual machine stats.
|
Story Points: | --- |
| Clone Of: | 1072282 | Environment: | |
| Last Closed: | 2014-04-09 17:58:44 UTC | Type: | --- |
| 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: | 1072282 | ||
| Bug Blocks: | |||
|
Comment 2
Artyom
2014-03-20 14:02:37 UTC
This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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-0384.html |