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.

remove a cluster from luci, then create a new cluster with a new name, including the old nodes:

The following errors occurred while creating cluster "fabbione-rhel6": rhel6-node1 is already a member of a cluster named "fabbione", rhel6-node2 is already a member of a cluster named "fabbione"

It appears that this error is coming from ricci.

sequence: start cluster with old name, remove cluster from luci,
cluster.conf is not wiped from the nodes and ricci still reads the one on disk.

trying to create the new cluster (that at this point should be legal) with a new name re-using the old nodes fails because of ricci on the node still looking at the old config.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

forgot to mention, this is using the latest code from luci.git

Right now when you delete a cluster, it only deletes it from luci.  It doesn't delete it from the nodes.  This is by design.  Otherwise there is no way to remove a cluster from luci.  We should probably include a "Destroy" cluster option that will remove the nodes from the cluster and removed the cluster.conf files.

I'll create a new bug with that option (616239).