Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Consider for RHEL 7 since this is most likely verification-only.
+++ This bug was initially created as a clone of Bug #1919057 +++
Description of problem:
This is a request to support using fence_mpath and fence_scsi to manage SCSI persistent reservations on SPC-4-compliant devices. Both of these fence agents use the sg_persist command to manage reservations and keys. The `sg_persist(8)` man page suggests that it's compatible with SPC-4, so this probably only requires QA verification.
-----
Version-Release number of selected component (if applicable):
fence-agents-mpath-4.2.1-53.el8_3.1
fence-agents-scsi-4.2.1-53.el8_3.1
-----
How reproducible:
N/A
-----
Steps to Reproduce:
Test fence_mpath and fence_scsi fence agents managing SCSI persistent reservations on SPC-4-compliant devices.
-----
Expected results:
All tests pass -- that is, the agents behave the same with SPC-4 as with SPC-3 (currently supported).
--- Additional comment from Reid Wahl on 2021-01-22 02:01:25 UTC ---
Thread:
- http://post-office.corp.redhat.com/archives/sbr-clusterha/2020-June/msg00059.html
Someone asked me about this today, and I realized I never opened the BZ.
--- Additional comment from Reid Wahl on 2021-01-22 02:04:16 UTC ---
Thoughts on cloning this for RHEL 7? Generally speaking, RFEs are a no-go. I ask because this is most likely verification-only.
--- Additional comment from Oyvind Albrigtsen on 2021-01-22 12:37:17 UTC ---
You can clone it to RHEL7, and just add "Consider for RHEL7" to the top of the description.
Comment 10Kevin P. Fleming
2022-02-24 19:29:46 UTC
This BZ is over a year old and hasn't had any activity from the reporter or any other non-bot account. If this feature backport is still desired, please follow the process to request an exception. If not, please close this BZ. Thanks.
Comment 15RHEL Program Management
2023-09-22 18:59:33 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 16RHEL Program Management
2023-09-22 19:00:05 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.