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.

Description of problem:
Removing cluster in luci will not stop cman on nodes nor delete cluster.conf on
nodes. This will prevent creating cluster with same nodes again. It is because
luci does not really care about whether the cluster is or is not running but it
appears that it does. 

Version-Release number of selected component (if applicable):
luci-0.26.0-13.el6.x86_64

How reproducible: 
always

Steps to Reproduce:
1. create cluster, check: reboot before joinining, shared storage, download packages
2. wait for luci to create cluster
3. delete cluster
4. create cluster again
  
Actual results:
The following errors occurred while creating cluster "cluster": rhel62-node01
is already a member of a cluster named "rhel62", rhel62-node02 is already a
member of a cluster named "rhel62", rhel62-node03 is already a member of a
cluster named "rhel62"

Expected results:
Cluster happily created.

Additional info:
This persists between luci restarts. I believe that it would be good idea to
provide checklist to remove cluster.conf or at least provide information that 
removing cluster from luci does not influence cluster itself.

This was already a subject of [bug 616239] in the past;  the solution
here is probably to delete all the nodes simultaneously.  If you find
this use case counter-intuitive, please consult the documentation
(filing the bug for it if this use case is missing) and perhap suggest
an incremental enhancement while not throwing "the old way" overboard
if possible (and if it makes sense).

This is the way it's supposed to work. Remove cluster only removes the cluster from luci and does not destroy the cluster itself.

I had a closer look into the documentation and it is really well explained in "RHEL6: Cluster Administration", chapter "4.2. Removing a Cluster from the luci Interface".

I'm closing this as NOTABUG.