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 2001024 - [RFE] RHEL9 support fence agent based on NVME reservation
Summary: [RFE] RHEL9 support fence agent based on NVME reservation
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: fence-agents
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.3
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe
URL:
Whiteboard: NVMe_P2
Depends On:
Blocks: 2116239 2188515
TreeView+ depends on / blocked
 
Reported: 2021-09-03 14:58 UTC by vincent chen
Modified: 2023-09-22 20:47 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 20:47:35 UTC
Type: Story
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7749 0 None Migrated None 2023-09-22 20:47:29 UTC
Red Hat Issue Tracker RHELPLAN-96163 0 None None None 2023-03-03 07:29:57 UTC

Description vincent chen 2021-09-03 14:58:40 UTC
Description of problem:
does RHCS in rhel9.0  support fence agent based on NVME reservation. I don't see any info about it?  
storage reservation is an important method to fence node from storage view. wish there could have nvme based PR fence agent in RHCS 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 RHEL Program Management 2023-03-03 07:27:53 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 vincent chen 2023-04-12 02:52:04 UTC
Karl,  this is a public requirement. not dell specific.   thinking about RHCS support scsi_fence mechanism which depending on storage vender supporting scsi reservation standards. now nvme-F is more and more popular and dell storage already support nvme reservation standard too. so we ask if rhel has a plan support to support nvme_fence  agent.

Comment 9 John Meneghini 2023-05-04 03:11:33 UTC
The nvme replacement for sg3_utils with is the nvme-cli utility.  This utility is fully supported by RHEL.

 [root@rhel-storage-105 ~]# rpm -qi nvme-cli
 Name        : nvme-cli
 Version     : 2.4
 Release     : 1.el9
 Architecture: x86_64
 Install Date: Tue 18 Apr 2023 05:40:34 PM EDT
 Group       : Unspecified
 Size        : 4982802
 License     : GPLv2+
 Signature   : RSA/SHA256, Wed 12 Apr 2023 03:55:03 AM EDT, Key ID 199e2f91fd431d51
 Source RPM  : nvme-cli-2.4-1.el9.src.rpm
 Build Date  : Thu 06 Apr 2023 06:25:43 AM EDT
 Build Host  : x86-64-06.build.eng.rdu2.redhat.com
 Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
 Vendor      : Red Hat, Inc.
 URL         : https://github.com/linux-nvme/nvme-cli
 Summary     : NVMe management command line interface
 Description :
 nvme-cli provides NVM-Express user space tooling for Linux.

So, instead of using the `sg_persist` command you would use the `nvme` command to manage reservations on the nvme device.

  resv-acquire                 Submit a Reservation Acquire, return results
  resv-register                Submit a Reservation Register, return results
  resv-release                 Submit a Reservation Release, return results
  resv-report                  Submit a Reservation Report, return results

This means:

 sg_persist --out --register --param-rk=123456 /dev/sdb

becomes:

 nvme resv-register /dev/nvme1n1 --rrega=0 --nrkey=123456 --iekey

Example:

[root@rhel-storage-105 ~]# nvme resv-register /dev/nvme1n1 --rrega=0 --nrkey=123456 --iekey
NVME Reservation  success
[root@rhel-storage-105 ~]# nvme resv-report /dev/nvme1n1

NVME Reservation status:

gen       : 1
rtype     : 0
regctl    : 1
ptpls     : 1
regctl[0] :
  cntlid  : 1
  rcsts   : 0
  hostid  : 0
  rkey    : 1e240

Comment 10 vincent chen 2023-05-04 03:28:18 UTC
yes, the nvme-cli utility is supported by RHEL.  RHCS supply scsi_fence agent for cluster fencing. it only serve for scsi3 reservation.  there don't have a agent used for nvme reservation. there need a similar agent for nvme reservation

Comment 14 RHEL Program Management 2023-09-22 20:46:34 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 15 RHEL Program Management 2023-09-22 20:47: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.