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.

YKD provides solutions for some scenarios currently provided by qdisk but using network transports instead.

Investigate feasibility of adding YKD into the cluster stack for rhel7 target.

This feature request did not get resolved in time for Feature Freeze
for the current Red Hat Enterprise Linux release and has now been
denied. It has been proposed for the next Red Hat Enterprise Linux
release.

**  If you would still like this feature request considered for
the current release, please ask your support representative to
file an exception on your behalf.  **

Even YKD can be interesting, we've improved votequorum A LOT, so this feature has very low priority now. Moving to 7.1 for future review.

I would recommend just closing this feature and dropping YKD from the list of things on the radar.  votequorum gets the job done, and the need for ykd seems minimal imo.

(In reply to Steven Dake from comment #6)
> I would recommend just closing this feature and dropping YKD from the list
> of things on the radar.  votequorum gets the job done, and the need for ykd
> seems minimal imo.

Agreed. We are not going to support 2 quorum mechanisms.