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 1814962 - No persistent reservation manager when blockcopy to scsi pr destination
Summary: No persistent reservation manager when blockcopy to scsi pr destination
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Han Han
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-19 06:45 UTC by Han Han
Modified: 2023-09-22 16:19 UTC (History)
11 users (show)

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

Attachments (Terms of Use)
libvirtd log of step4, VM xml, disk dest xml (15.50 KB, application/gzip)
2020-03-19 06:45 UTC, Han Han 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7342 0 None Migrated None 2023-09-22 16:19:28 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.