Bug 609417 - [vdsm] [libvirt intg] in case vm is paused due to unknown reason by libvirt it remains "up" in vdsm
[vdsm] [libvirt intg] in case vm is paused due to unknown reason by libvirt i...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm (Show other bugs)
6.1
All Linux
low Severity high
: rc
: ---
Assigned To: Dan Kenigsberg
Moran Goldboim
vdsm * libvirt integration
:
Depends On:
Blocks: 581275
  Show dependency treegraph
 
Reported: 2010-06-30 04:56 EDT by Haim
Modified: 2014-01-12 19:46 EST (History)
6 users (show)

See Also:
Fixed In Version: vdsm-4.9-10.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-08-19 11:22:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Haim 2010-06-30 04:56:09 EDT
Description of problem:

there are some conditions where libvirt decides to pause vm (e_no_space for example) and if event is not properly handled by vdsm, then vm will go to pause from libvirt side, but will remain up by vdsm and as a result rhev-m side. 
i know we can't deal with all cases, but at least we should say that in case that pause event is not handled correctly, put vm into pause.


Version-Release number of selected component (if applicable):

vdsm-4.9-9.2.x86_64
qemu-kvm-0.12.1.2-2.82.el6.x86_64
2.6.32-37.el6.x86_64

How reproducible: run scenario of lvextend on iscsi with sparse allocation - currently it's not dealt correctly, so you will hit this scenario.
Comment 2 RHEL Product and Program Management 2010-06-30 05:23:08 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 Haim 2010-07-30 04:28:52 EDT
Dan, how can I test this flow ? libvirt now handles the enospace event, can you provide me some code to test it ?
Comment 5 Dan Kenigsberg 2010-08-01 03:01:56 EDT
Haim, I told you not to open this bug...

You can comment out the lines
        elif eventid == libvirt.VIR_DOMAIN_EVENT_ID_IO_ERROR_REASON:
            srcPath, devAlias, action, reason = args[:-1]
            v._onAbnormalStop(devAlias, reason)
in libvirtvm.py. The VM should go to Paused even without them.
Comment 6 Haim 2010-08-19 03:14:38 EDT
Dan, we have another unhanded case which creates this state where 'qemu' produces 'eother' error reason (with UDEV case). 

what do you think ?
Comment 7 Dan Kenigsberg 2010-08-19 03:23:45 EDT
let the eother be tracked by its specific BZ. This issue is much more general.
Comment 8 Haim 2010-08-19 03:38:23 EDT
verified then, it only occurs with 'eother' sate. 

2.6.32-59.1.el6.x86_64
libvirt-0.8.1-25.el6.x86_64
vdsm-4.9-13.el6.x86_64
device-mapper-multipath-0.4.9-25.el6.x86_64
lvm2-2.02.72-7.el6.x86_64
qemu-kvm-0.12.1.2-2.109.el6.x86_64

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