Bug 1391506
| Summary: | [z-stream clone - 4.0.6] Periodic functions may continue running after VM is down. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | vdsm | Assignee: | Francesco Romani <fromani> |
| Status: | CLOSED ERRATA | QA Contact: | sefi litmanovich <slitmano> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.8 | CC: | bazulay, fromani, gklein, gveitmic, lsurette, mburman, mgoldboi, michal.skrivanek, mzamazal, obockows, srevivo, tjelinek, trichard, ycui, ykaul |
| Target Milestone: | ovirt-4.0.6 | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
Previously, if a virtual machine shutdown was too slow, the state of the virtual machine could have been misreported as unresponsive, even though the virtual machine was operating correctly, albeit too slowly. This was caused by a too-aggressive checking on startup and shutdown. This patch takes into account slowdowns in startup and shutdown, avoiding false positive reports.
|
Story Points: | --- |
| Clone Of: | 1382578 | Environment: | |
| Last Closed: | 2017-01-10 17:02:04 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: | 1382578 | ||
| Bug Blocks: | |||
|
Comment 2
Michal Skrivanek
2016-11-03 13:07:12 UTC
*** Bug 1391505 has been marked as a duplicate of this bug. *** Verified using host with vdsm-4.18.16-1.el7ev.x86_64 on a rhevm-4.0.6-0.1.el7ev.noarch after saw the bug and re produced on two different envs (one with older 4.18.x vdsm and one with 4.17.y vdsm. With this fix, after monitoring vdsm.log for several hours and starting and stopping 8 vms on and off, I didn't get the 'monitor become unresponsive' WARNING as I did get every few minutes with the other vdsms right after a vm is shutdown, so seems to me this is fixed. 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://rhn.redhat.com/errata/RHBA-2017-0044.html |