Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 692681

Summary: [libvirt] libvirt returns 'VIR_ERR_OPERATION_INVALID' after migration along with 'VIR_ERR_NO_DOMAIN'
Product: Red Hat Enterprise Linux 6 Reporter: Haim <hateya>
Component: libvirtAssignee: Michal Privoznik <mprivozn>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: abaron, dallan, danken, dnaori, eblake, mgoldboi, yeylon, yoyzhang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-22 08:11:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 618986, 682015    

Description Haim 2011-03-31 20:21:59 UTC
Description of problem

on migration scenario, libvirt sends the following events to vdsm in case vdsm tries to query blockstats on not running vm: 

'VIR_ERR_NO_DOMAIN = 42' and 'VIR_ERR_OPERATION_INVALID = 55'. 

This state confuses VDSM and as a result its prints a traceback to logs whenever migration occurs (successfully of course).

we added some logging in vdsm log during migration scenario and got the following: 

Thread-52::ERROR::2011-03-31 11:01:45,844::libvirtconnection::73::vds::(wrapper) ### Requested operation is not valid: domain is not running
Thread-52::ERROR::2011-03-31 11:01:45,845::libvirtconnection::74::vds::(wrapper) ### 55
Thread-66::ERROR::2011-03-31 11:01:45,849::libvirtconnection::73::vds::(wrapper) ### Domain not found: no domain with matching uuid 'd9cab512-5438-48ff-8f55-d600cc883be7'
Thread-66::ERROR::2011-03-31 11:01:45,850::libvirtconnection::74::vds::(wrapper) ### 42
Thread-66::ERROR::2011-03-31 11:01:45,859::libvirtconnection::73::vds::(wrapper) ### Domain not found: no domain with matching uuid 'd9cab512-5438-48ff-8f55-d600cc883be7'
Thread-66::ERROR::2011-03-31 11:01:45,859::libvirtconnection::74::vds::(wrapper) ### 42
Thread-76::ERROR::2011-03-31 11:01:51,903::libvirtconnection::73::vds::(wrapper) ### Domain not found: no domain with matching uuid 'd9cab512-5438-48ff-8f55-d600cc883be7'
Thread-76::ERROR::2011-03-31 11:01:51,903::libvirtconnection::74::vds::(wrapper) ### 42

attached libvirt logs.

Comment 1 RHEL Program Management 2011-04-04 02:05:22 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 2 Michal Privoznik 2011-04-29 15:04:59 UTC
Haim,

could you please attach those logs?

Comment 3 Dave Allan 2011-05-06 14:29:43 UTC
Hi Haim, it looks like you thought you attached the logs, but they are not attached.  Can you provide them?  Thanks, Dave