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 1203628 - Libvirt should post error when try to create external snapshot while there is a blockpull job running
Summary: Libvirt should post error when try to create external snapshot while there is...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-19 09:55 UTC by Shanzhi Yu
Modified: 2015-11-19 06:20 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.2.15-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 06:20:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2202 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2015-11-19 08:17:58 UTC

Description Shanzhi Yu 2015-03-19 09:55:16 UTC 
Description of problem:

Libvirt should post error when try to create external snapshot while there is a blockpull job running

Version-Release number of selected component (if applicable):
libvirt-1.2.8-16.el7_1.2.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a blockpull job for guest
# virsh blockpull vm vda --bandwidth 1 --verbose --wait 
Block Pull: [ 19 %]

2. Try to create external disk snapshot

# virsh snapshot-create-as vm ss2 --disk-only --no-metadata 
error: internal error: unable to execute QEMU command 'transaction': Device 'drive-virtio-disk0' is busy: block device is in use by block job: stream

3.

Actual results:


Expected results:

More accurate error info like:

# virsh snapshot-create-as vm ss2 --disk-only --no-metadata 
error: block copy still active: domain has active block job

Additional info:
Comment 1 Peter Krempa 2015-04-02 08:47:51 UTC 
Fixed upstream:

commit c2a81eb7e16309634864843c3aacb75be9023f70
Author: Peter Krempa <pkrempa>
Date:   Mon Mar 30 20:16:45 2015 +0200

    qemu: snapshot: Check for block jobs individually
    
    If any disk of a VM was involved in a (copy) block job we refused to do
    a snapshot. As not only copy jobs interlock snapshots and the
    interlocking is applicable to individual disks only we can make the
    check in a more individual fashion and interlock all block job types
    supported by libvirt.

v1.2.14-16-gc2a81eb
Comment 3 Yang Yang 2015-05-25 02:39:24 UTC 
Verified on libvirt-1.2.15-2.el7.x86_64

Steps
1. create snapshot during blockpull
# virsh blockpull simple vda --wait --verbose --bandwidth 1
Block Pull: [  1 %]

# virsh snapshot-create-as simple s4 --disk-only --diskspec vda,file=/tmp/s4 --diskspec hdb,snapshot=no
error: unsupported configuration: disk 'vda' has an active block job

2. create snapshot during blockcommit
# virsh blockcommit simple vda --active --wait --verbose --bandwidth 1
Block Commit: [  6 %]

# virsh snapshot-create-as simple s4 --disk-only --diskspec vda,file=/tmp/s4 --diskspec hdb,snapshot=no
error: unsupported configuration: disk 'vda' has an active block job

3. create snapshot during blockcopy
# virsh blockcopy simple vda --wait --verbose /tmp/copy --bandwidth 1
Block Copy: [  1 %]

# virsh snapshot-create-as simple s4 --disk-only --diskspec vda,file=/tmp/s4 --diskspec hdb,snapshot=no
error: unsupported configuration: disk 'vda' has an active block job
Comment 5 errata-xmlrpc 2015-11-19 06:20:42 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/RHBA-2015-2202.html
Note You need to log in before you can comment on or make changes to this bug.