Bug 2087074

Summary: Fail to do blockcopy to target device after forbid doing blockcopy to the same source device
Product: Red Hat Enterprise Linux 9 Reporter: aihua liang <aliang>
Component: libvirtAssignee: Peter Krempa <pkrempa>
libvirt sub component: Storage QA Contact: Meina Li <meili>
Status: CLOSED MIGRATED Docs Contact:
Severity: low    
Priority: low CC: jsuchane, kwolf, pkrempa, virt-maint, yafu
Version: 9.1Keywords: MigratedToJIRA, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 16:20:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm.xml none

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.