Bug 1814962

Summary: No persistent reservation manager when blockcopy to scsi pr destination
Product: Red Hat Enterprise Linux 9 Reporter: Han Han <hhan>
Component: libvirtAssignee: Virtualization Maintenance <virt-maint>
libvirt sub component: Storage QA Contact: Han Han <hhan>
Status: CLOSED MIGRATED Docs Contact:
Severity: medium    
Priority: medium CC: berrange, jsuchane, lmen, meili, mprivozn, pkrempa, reufrujevic750, virt-maint, xuzhang, yalzhang, yisun
Version: 9.0Keywords: MigratedToJIRA, Reopened, 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:19:35 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
libvirtd log of step4, VM xml, disk dest xml none

Description Han Han 2020-03-19 06:45:41 UTC
Created attachment 1671347 [details]
libvirtd log of step4, VM xml, disk dest xml

Description of problem:
As subject

Version-Release number of selected component (if applicable):
libvirt-6.0.0-13.virtcov.el8.x86_64
qemu-kvm-4.2.0-15.module+el8.2.0+6029+618ef2ec.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start a VM
2. Prepare a scsi disk for host.
3. Prepare a xml of scsi pr disk dest with luks format
# cat pr.xml 
<disk type="block" device="lun">
  <driver name="qemu" type="raw"/>
  <source dev="/dev/sdc">
    <reservations managed="yes"/>
  </source>
  <target dev="sda" bus="scsi"/>
</disk>

4. Do blockcopy
# virsh blockcopy new sda --xml pr.xml --pivot --transient-job --verbose --wait                                                                                                                            
error: internal error: unable to execute QEMU command 'blockdev-add': No persistent reservation manager with id 'pr-helper0'


Actual results:
As step4

Expected results:
pr-helper0 should be created for this blockcopy

Additional info:

Comment 5 John Ferlan 2021-09-08 13:31:38 UTC
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 6 Reuf Rujevic 2021-09-13 09:46:28 UTC Comment hidden (spam)
Comment 7 RHEL Program Management 2021-09-19 07:26:58 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 Meina Li 2022-11-25 05:37:12 UTC
Hi,

This bug can still be reproduced now. So I've reopened it. Do we have plan/requirement to implement it? If not, please help to close it as WONTFIX again. Thanks.

Test Version:
libvirt-8.9.0-2.el9.x86_64
qemu-kvm-7.1.0-5.el9.x86_64
qemu-pr-helper-7.1.0-5.el9.x86_64

Test Steps:
1. Prepare a running guest.
# virsh domstate test
running

2. Prepare a target disk xml.
# cat disk.xml
<disk type="block" device="lun">
  <driver name="qemu" type="raw"/>
  <source dev="/dev/sdb">
    <reservations managed="yes"/>
  </source>
  <target dev="sda" bus="scsi"/>
</disk>

3. Do blockcopy.
# virsh blockcopy test vda --xml disk.xml --transient-job 
error: internal error: unable to execute QEMU command 'blockdev-add': No persistent reservation manager with id 'pr-helper0'

Comment 11 Han Han 2023-05-09 03:39:58 UTC
Hi Peter,
Please help look at this bug. It is not update since reported.

Comment 12 Peter Krempa 2023-05-09 08:07:25 UTC
(In reply to Han Han from comment #11)
> Hi Peter,
> Please help look at this bug. It is not update since reported.

It's on the backlog as it's low priority.

Comment 13 RHEL Program Management 2023-09-22 16:18:21 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 14 RHEL Program Management 2023-09-22 16:19:35 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.