Bug 1342388
| Summary: | VM split brain during networking issues | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ | |
| Component: | ovirt-engine | Assignee: | Arik <ahadas> | |
| Status: | CLOSED ERRATA | QA Contact: | Nisim Simsolo <nsimsolo> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.6.0 | CC: | agkesos, ahadas, amarchuk, bgraveno, emahoney, fromani, jentrena, lsurette, mgoldboi, michal.skrivanek, mkalinin, mtessun, nsimsolo, pkliczew, pstehlik, rbalakri, Rhev-m-bugs, rhodain, srevivo, stirabos, tdosek, ykaul | |
| Target Milestone: | ovirt-3.6.7 | Keywords: | ZStream | |
| Target Release: | 3.6.7 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Previously during vdsm restart, the host would still respond to queries over JSON-RPC protocol from the Manager, which could result in the Manager reporting the incorrect virtual machine state. This could cause a highly available virtual machine to restart despite it already running. This has been fixed and the API calls are blocked during the vdsm service startup.
|
Story Points: | --- | |
| Clone Of: | 1339291 | |||
| : | 1344075 (view as bug list) | Environment: | ||
| Last Closed: | 2016-06-29 16:20:35 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1339291 | |||
| Bug Blocks: | 1344075 | |||
|
Comment 2
Francesco Romani
2016-06-07 12:18:48 UTC
the Vdsm changes do not require doc_string updates. one more petch needs to get in:) https://gerrit.ovirt.org/#/c/58465/ *** Bug 1337203 has been marked as a duplicate of this bug. *** Verification builds: rhevm-3.6.7.5-0.1.el6 libvirt-client-1.2.17-13.el7_2.5.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 vdsm-4.17.31-0.el7ev.noarch sanlock-3.2.4-2.el7_2.x86_64 Verification scenarios: # Add 60 seconds sleep /usr/share/vdsm/clientIf.py (the scenario of reproducing this bug before the fix): 1. Use 2 hosts under the same cluster, on SPM host edit /usr/share/vdsm/clientIf.p and add time.sleep(60) under def _recoverExistingVms(self): 2. enable HA on VM. 3. Run VM. 4. Restart vdsmd service (look for "VM is running in db and not running in VDS 'hostname'" in engine.log). 5. Verify VM is not migrating to the second host. After VDSM service restarted, verify same qemu-kvm process is running on SPM host and verify no qemu-kvm process for same VM on the second host. Verify VM continue to run properly. # Stop VDSM service: 1. Stop VDSM service on the host with running VM. 2. Wait for host to become non-responsive and VM in unknown state. 3. Verify soft fencing started on the host and VM status restored to up. 4. Verify VM continue to run properly. # Power off host: 1. Power off host with VM running on it. 2. Wait for host to become in non-responsive state and VM in unknown state. 3. From webadmin confirm 'host has been rebooted'. 4. Verify VM is migrating to the active host and VM is restarting. 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. https://access.redhat.com/errata/RHBA-2016:1364 *** Bug 1452393 has been marked as a duplicate of this bug. *** |