Bug 1163142 - Pending resources are not cleared when network exception occurs.
Summary: Pending resources are not cleared when network exception occurs.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: x86_64
OS: Unspecified
medium
urgent
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks: 1174817
TreeView+ depends on / blocked
 
Reported: 2014-11-12 12:42 UTC by Nisim Simsolo
Modified: 2016-04-20 01:25 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1174817 (view as bug list)
Environment:
Last Closed: 2016-04-20 01:25:26 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine logs (11.60 MB, application/x-xz)
2014-11-12 12:44 UTC, Nisim Simsolo
no flags Details
vdsm.log (7.54 MB, text/plain)
2014-11-12 12:46 UTC, Nisim Simsolo
no flags Details
libvirtd.log (963.89 KB, text/plain)
2014-11-12 12:46 UTC, Nisim Simsolo
no flags Details
snalock.log (179.85 KB, text/plain)
2014-11-12 12:47 UTC, Nisim Simsolo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 35890 0 master MERGED core: improve exception handling on run vm 2020-10-01 10:52:16 UTC

Description Nisim Simsolo 2014-11-12 12:42:41 UTC
Description of problem:
When netork exception occurs (such as bug https://bugzilla.redhat.com/show_bug.cgi?id=1163073) pending resoured are not cleared, eventually cause to insufficiant resources in host while trying to add VM.

Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.19.beta.el6ev.noarch
libvirt-0.10.2-46.el6_6.1.x86_64
sanlock-2.8-1.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
vdsm-4.16.7.3-1.el6ev.x86_64

How reproducible:
inconsistently, depends on bug 1163073.

Steps to Reproduce:
1. Using vt9 release, add few VMs and run them.
2. In case of VM get stuck in launching state or failed to launch, try to remove VM and add another one.
3. Observe host "Max free Memory for scheduling new VM" or pending resources in engine databse.

Actual results:
resources are not cleared in case of VM start failure due to network exception.

Expected results:
resources should be cleared in case of VM failed to start.

Additional info:
Enging and host logs attached.

Comment 1 Nisim Simsolo 2014-11-12 12:44:06 UTC
Created attachment 956727 [details]
engine logs

Comment 2 Nisim Simsolo 2014-11-12 12:46:09 UTC
Created attachment 956728 [details]
vdsm.log

Comment 3 Nisim Simsolo 2014-11-12 12:46:50 UTC
Created attachment 956730 [details]
libvirtd.log

Comment 4 Nisim Simsolo 2014-11-12 12:47:18 UTC
Created attachment 956732 [details]
snalock.log

Comment 7 Nisim Simsolo 2015-05-21 14:16:57 UTC
Verified, oVirt Engine Version: 3.6.0-0.0.master.20150412172306.git55ba764.el6


Note You need to log in before you can comment on or make changes to this bug.