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 1059904 - Inconsistent blockInfo values when the VM is finalizing live migration
Summary: Inconsistent blockInfo values when the VM is finalizing live migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: John Ferlan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1040507 1065531
Blocks: 871829 1038069
TreeView+ depends on / blocked
 
Reported: 2014-01-30 22:09 UTC by Chris Pelland
Modified: 2014-04-22 12:13 UTC (History)
25 users (show)

Fixed In Version: libvirt-0.10.2-29.el6_5.4
Doc Type: Bug Fix
Doc Text:
Cause: Migration of transient guests returned the default "allocation" virDomainBlockInfo value for a qcow2 block backed device instead of the actual from a virDomainGetBlockInfo() call in a brief instance between when libvirt declared the guest migrated and performing the guest removal. Consequence: Applications that depended upon a non default value being returned may take the wrong action, such as extending the logical volume since the allocation would be the same as physical. Fix: When the condition is detected for a transient domain return a failure. Result: The virDomainGetBlockInfo() will fail with the error "domain is not running" for a transient domain once the migration has successfully completed and before the domain is destroyed on the source.
Clone Of:
Environment:
Last Closed: 2014-02-20 09:50:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0193 0 normal SHIPPED_LIVE libvirt bug fix update 2014-02-20 14:49:01 UTC

Description Chris Pelland 2014-01-30 22:09:42 UTC 
This bug has been copied from bug #1040507 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 8 EricLee 2014-02-13 09:48:35 UTC 
Hi Federico,

We are trying to verify this bug, but we can not reproduce the bug under pure libvirt environment. So can you help to have a try with the package libvirt-0.10.2-29.el6_5.4 in rhevm?

I think the expected result should fail to get domblkinfo with error info including "domain is not running".

Thanks in advance.

EircLee
Comment 9 David Jaša 2014-02-13 14:34:32 UTC 
The libvirt-0.10.2-29.el6_5.4 build fixes the original issue: doesn't occur anymore on environment where it was spotted first when libvirt in both hosts is updated to this version.
Comment 10 EricLee 2014-02-14 07:33:50 UTC 
(In reply to David Jaša from comment #9)
> The libvirt-0.10.2-29.el6_5.4 build fixes the original issue: doesn't occur
> anymore on environment where it was spotted first when libvirt in both hosts
> is updated to this version.

Thanks for the test.

John,

Do you think that enough to verify this bug? Or we need catch the error info:"domain is not running"?

Thanks,
EricLee
Comment 11 John Ferlan 2014-02-14 10:54:01 UTC 
Since the problem was seen in the rhev test environment primarily and they indicate the patch works, I think that's good enough.  The error message about domain is not running would be somewhat generic - you may not know that it came from this path.  Returning the error though results in their thread no fetching data which ultimately is what led to the issue.


If you're more curious about the core issue see the bz this was copied from (bz 1040507).
Comment 12 EricLee 2014-02-14 15:29:35 UTC 
Thanks John.

Setting VERIFIED as comment #9 and comment #11.
Comment 14 errata-xmlrpc 2014-02-20 09:50:23 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.

http://rhn.redhat.com/errata/RHBA-2014-0193.html
Note You need to log in before you can comment on or make changes to this bug.