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.

Steven, I haven't finished deducing the changes from cluster schemas diff
between RHEL 6.6 and 6.7 yet, but take this as "early" heads up that
there are plenty of changes regarding fence agents, so a lot of updates
to the respective appendix may be needed.

As a starter, please take a look at [bug 1210679 comment 11]; quoting
the final part:

> New fence agents (if I am not missing anything):
> 
> fence_emerson
> fence_ilo3_ssh
> fence_ilo4_ssh
> fence_ilo_moonshot
> fence_ilo_ssh
> fence_mpath
> fence_tripplite_snmp

Any reasonable new findings will be posted to that original bug.


+++ This bug was initially created as a clone of Bug #1210679 +++

These won't make the original Beta -- I was waiting for this to appear in luci -- since my deadline is today for that release. BUT I can actually update the version of the document on the Portal at any time so as soon as these go in luci and I add them to the doc I can update the Beta version.