Bug 2232090

Summary:	'pcs booth destroy' command only works for hosts with a running cluster
Product:	Red Hat Enterprise Linux 9	Reporter:	Tomas Jelinek <tojeline>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0	CC:	cluster-maint, idevat, mlisik, mpospisi, omular, tojeline
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	9.4	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 20:34:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2023-08-15 09:17:27 UTC

Description of problem:
The 'pcs booth destroy' command is supposed to remove booth configuration files (config and key) from a node, regardless if it is a site node or an arbitrator node. The command implements various checks to prevent removing booth configuration in case it is being actively used by a running instance of booth. One of the check is bugged, as it requires CIB to be accessible, which makes the command not working on arbitrators and nodes with no cluster.


Version-Release number of selected component (if applicable):
pcs-0.10.0


How reproducible:
always, easily


Steps to Reproduce:
1. get a host with no running cluster
2. run 'pcs booth destroy'


Actual results:
Error: unable to get cib


Expected results:
If CIB cannot be obtained, it means either the cluster is stopped on the node, or the node serves as an arbitrator. The command should proceed and check if the booth config is used by a running arbitrator service on the node. If the config is not used, it should be deleted including related key file.

Comment 1 RHEL Program Management 2023-09-22 20:33:39 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 2 RHEL Program Management 2023-09-22 20:34:36 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.