Bug 1346848 - VmPoolMonitor does not log reason for VM prestart failure
Summary: VmPoolMonitor does not log reason for VM prestart failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.0.2
: 4.0.2
Assignee: jniederm
QA Contact: sefi litmanovich
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-15 13:01 UTC by Roman Hodain
Modified: 2019-11-14 08:26 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
This update fixes the message logging when failing to prestart a pool virtual machine. The log message will now print the reason for the failure, and it has been raised from an INFO to a WARN log message. The log message now contains the ID of the failed virtual machine.
Clone Of: 1346270
Environment:
Last Closed: 2016-08-23 20:42:48 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 RHEA-2016:1743 0 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 21:54:01 UTC
oVirt gerrit 51005 0 None None None 2016-07-07 06:58:59 UTC
oVirt gerrit 60144 0 master MERGED core: Logging of VmPoolMonitor fixed 2016-07-14 06:43:04 UTC
oVirt gerrit 60994 0 ovirt-engine-4.0 MERGED core: Logging of VmPoolMonitor fixed 2016-07-19 12:54:54 UTC

Comment 2 jniederm 2016-07-04 15:24:26 UTC 
Note on image locking: Use all_disks.vm_names and all_disks.image_guid to find image id lock it by setting 2 in column images.imagestatus.
Comment 3 sefi litmanovich 2016-08-01 12:36:55 UTC 
Verified with rhevm-4.0.2.1-0.1.el7ev.noarch according to steps to re produce in description. The Warning messages appear as expected in engine.log.
Comment 5 errata-xmlrpc 2016-08-23 20:42:48 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/RHEA-2016-1743.html
Note You need to log in before you can comment on or make changes to this bug.