Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1391506 - [z-stream clone - 4.0.6] Periodic functions may continue running after VM is down.
[z-stream clone - 4.0.6] Periodic functions may continue running after VM is ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
3.6.8
Unspecified Unspecified
high Severity high
: ovirt-4.0.6
: ---
Assigned To: Francesco Romani
sefi litmanovich
: ZStream
: 1391505 (view as bug list)
Depends On: 1382578
Blocks:
  Show dependency tree / graph
 
Reported: 2016-11-03 08:55 EDT by rhev-integ
Modified: 2017-04-03 08:39 EDT (History)
15 users (show)

See Also:
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 12:02:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 65814 None None None 2016-11-03 08:56 EDT
Red Hat Product Errata RHBA-2017:0044 normal SHIPPED_LIVE vdsm 4.0.6 bug fix and enhancement update 2017-01-10 16:52:50 EST

  None (edit)
Comment 2 Michal Skrivanek 2016-11-03 09:07:12 EDT 
modified in 4.0.6 already
Comment 3 Michal Skrivanek 2016-11-04 02:02:01 EDT 
*** Bug 1391505 has been marked as a duplicate of this bug. ***
Comment 4 sefi litmanovich 2016-11-27 08:54:42 EST 
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.
Comment 6 errata-xmlrpc 2017-01-10 12:02:04 EST 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.