Bug 1298190 - Vm.status() causes crash of MoM GuestManager
Summary: Vm.status() causes crash of MoM GuestManager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.5.8
: ---
Assignee: Francesco Romani
QA Contact: Shira Maximov
URL:
Whiteboard:
Depends On: 1296936
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-13 12:38 UTC by rhev-integ
Modified: 2020-08-04 09:38 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, in certain cases the MOM component stopped enforcing QoS policies, KSM, and memory ballooning. This has now been fixed.
Clone Of: 1296936
Environment:
Last Closed: 2016-02-29 14:50:01 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0317 0 normal SHIPPED_LIVE vdsm 3.5.8 - bug fix and enhancement update 2016-02-29 19:48:53 UTC
oVirt gerrit 51655 0 master MERGED migration: use context manager for semaphore 2016-01-13 19:45:33 UTC
oVirt gerrit 51656 0 master MERGED virt: safer handling of migration parameters 2016-01-13 19:49:26 UTC
oVirt gerrit 52341 0 ovirt-3.5 MERGED migration: use context manager for semaphore 2016-01-19 09:16:46 UTC
oVirt gerrit 52342 0 ovirt-3.5 MERGED virt: safer handling of migration parameters 2016-01-19 09:17:28 UTC
oVirt gerrit 52343 0 ovirt-3.5 MERGED vm: safer handling of conf in restore 2016-01-19 09:18:19 UTC

Comment 3 Shira Maximov 2016-02-04 13:38:12 UTC 
verified on 3.5.8 (mom-0.4.1-4.el6ev.noarch)

verification steps: 
1. create a pool of 15 VMs 
2. migrate all the 15 VMs 
3. check in mom logs

to be sure, i repeated this steps several times.
i didn't see this exception.
Comment 12 errata-xmlrpc 2016-02-29 14:50:01 UTC 
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-2016-0317.html
Note You need to log in before you can comment on or make changes to this bug.