This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2087074 - Fail to do blockcopy to target device after forbid doing blockcopy to the same source device
Summary: Fail to do blockcopy to target device after forbid doing blockcopy to the sam...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Meina Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-17 09:11 UTC by aihua liang
Modified: 2023-09-22 16:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 16:20:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
vm.xml (2.67 KB, text/plain)
2022-05-17 09:11 UTC, aihua liang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7357 0 None Migrated None 2023-09-22 16:19:59 UTC
Red Hat Issue Tracker RHELPLAN-122327 0 None None None 2022-05-17 09:25:52 UTC

Description aihua liang 2022-05-17 09:11:35 UTC 
Created attachment 1880418 [details]
vm.xml

Description of problem:
 Fail to do blockcopy to target device after forbid doing blockcopy to the same source device

Version-Release number of selected component (if applicable):
 qemu version:qemu-kvm-7.0.0-3.el9
 libvirt version:libvirt-8.3.0-1.el9.x86_64


How reproducible:
 100%

Steps to Reproduce:
1.Start guest rhel9
  #virsh define VM.xml
  #virsh start rhel9
Domain 'rhel9' started
  
2.Attach a scsi disk
  #cat /home/scsi.xml
   <disk type="block" device="lun">
  <driver name="qemu" type="raw" copy_on_read='off'/>
  <source dev="/dev/sdf">
    <reservations managed="yes"/>
  </source>
  <target dev="sdb" bus="scsi"/>
</disk>

 #virsh attach-device rhel9 /home/scsi.xml
Device attached successfully
 
 #virsh domblklist rhel9
 Target   Source
-----------------------------------------------------------------------
 vda      /home/kvm_autotest_root/images/rhel900-64-virtio-scsi.qcow2
 sdb      /dev/sdf

3.Do blockcopy to the same source device
 #virsh blockcopy rhel9 sdb /dev/sdf --blockdev --verbose --raw --transient-job --pivot
error: Requested operation is not valid: Setting different DAC user or group on /dev/sdf which is already in use

4.Do blockcopy to target device
 #virsh blockcopy rhel9 sdb /dev/sdg --blockdev --verbose --raw --transient-job --pivot
Block Copy: [100 %]error: failed to pivot job for disk sdb
error: operation failed: block job 'copy-sdb-libvirt-2-format' failed while pivoting

5.Check block status
 #virsh domblklist rhel9
 Target   Source
-----------------------------------------------------------------------
 vda      /home/kvm_autotest_root/images/rhel900-64-virtio-scsi.qcow2
 sdb      /dev/sdf

6.Destroy vm
 #virsh destroy rhel9 
Domain 'rhel9' destroyed

Actual results:
 In step4, failed to do blockcopy to target device.


Expected results:
 In step4, can do blockcopy to target device successfully.


Additional info:
 VM.xml and virtqemud.log as attachment.
Comment 2 aihua liang 2022-05-17 09:39:16 UTC 
Hi, Peter
 Track the new issue in bz1942803 here.
 Attachment is the virtqemud.log, not sure if it's you want.
 Please help to check if it's a libvirt bug? If not, please set Component: qemu-kvm and Sub Component: Block jobs.

Thanks,
Aliang
Comment 6 RHEL Program Management 2023-09-22 16:19:35 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-22 16:20:07 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.