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 2002488 - [RFE] fence_mpath, fence_scsi: Support for Azure shared disks
Summary: [RFE] fence_mpath, fence_scsi: Support for Azure shared disks
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fence-agents
Version: 8.4
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-09 01:12 UTC by Reid Wahl
Modified: 2023-09-22 19:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 19:02:20 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 KCSOPP-607 0 None None None 2022-06-27 21:35:51 UTC
Red Hat Issue Tracker   RHEL-7633 0 None Migrated None 2023-09-22 19:02:13 UTC
Red Hat Issue Tracker RHELPLAN-96604 0 None None None 2021-09-09 01:13:11 UTC
Red Hat Knowledge Base (Article) 3402391 0 None None None 2021-09-09 12:43:34 UTC

Description Reid Wahl 2021-09-09 01:12:34 UTC 
Description of problem:

The Microsoft documentation for Azure shared disks [1] states that Azure shared disks support SCSI persistent reservations, and that Microsoft expects these disks to support fence_scsi.

The Red Hat HA design guidance documentation [2] says regarding fence_mpath/fence_scsi on Azure VMs: "These methods are only suitable for clusters that host all cluster-managed application-data on SCSI-3-compatible shared block devices. No such shared devices are available in Azure environments, so these agents are incompatible with this platform."

It appears that with the introduction of Azure shared disks, this statement in the design guidance article is obsolete.

Note: I should point out that the Azure doc [1] says shared disks are supported on "RHEL developer preview on any RHEL 8 version". It's not clear to me what Microsoft means by this, so we should confer with them. The phrase quoted above is hyperlinked to a piece of Red Hat product documentation [3].


I would expect that fence_mpath/fence_scsi could be supported if:
  - Azure shared disks themselves are supported on RHEL 8, and
  - Azure shared disks implement SPC-3.

The SPC-3 requirement comes from our support policies [4]. It's worth noting that SPC-4 has been out for quite a while, but we don't yet officially support using fence_mpath/fence_scsi with disks that implement SPC-4, due to lack of testing so far [5]. SPC-5 also exists.

[1] https://docs.microsoft.com/en-us/azure/virtual-machines/disks-shared#linux
[2] Design Guidance for RHEL High Availability Clusters - Microsoft Azure Virtual Machines as Cluster Members (https://access.redhat.com/articles/3402391)
[3] Deploying Red Hat Enterprise Linux 8 on public cloud platforms | 2.15. Configuring shared block storage (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/deploying_red_hat_enterprise_linux_8_on_public_cloud_platforms/index?lb_target=production#azure-configuring-shared-block-storage_configuring-rhel-high-availability-on-azure)
[4] Support Policies for RHEL High Availability Clusters - fence_scsi and fence_mpath (https://access.redhat.com/articles/3078811)
[5] Bug 1919057 - [RFE] fence_mpath, fence_scsi: Support for SPC-4 disks [RHEL 8] (https://bugzilla.redhat.com/show_bug.cgi?id=1919057)
Comment 3 RHEL Program Management 2023-09-22 18:59:51 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 4 RHEL Program Management 2023-09-22 19:02:20 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.