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.
Bug 1722140 - Improve error message for 'pcs cluster node add' in case when adding node which is already part of another cluster configuration
Summary: Improve error message for 'pcs cluster node add' in case when adding node whi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-19 14:20 UTC by Miroslav Lisik
Modified: 2019-06-27 09:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-27 09:29:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1474747 0 medium CLOSED Confusing error message in both CLI and GUI after attempt to create cluster with node already in use 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1596050 1 None None None 2021-01-20 06:05:38 UTC

Description Miroslav Lisik 2019-06-19 14:20:08 UTC 
Description of problem:

Error message was improved in bz1474747 for case when cluster setup use node which is already part of another cluster configuration. Same improvement can be used for 'pcs cluster node add' command as it was in bz1596050.

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

pcs-0.9.167-2.el7

How reproducible:

always

Steps to Reproduce:

1. Setup two cluster A an B
2. Try to add node to cluster A from cluster B
3. See the error message

Actual results:

# pcs cluster node add virt-205
Error: Unable to add 'virt-205' to cluster: node is already in a cluster

Expected results:

Inform that you can force operation and that you should remove node from its current cluster e.g.:


Error: Unable to add 'virt-205' to cluster: node is already in a cluster, use --force to override. WARNING: This will destroy existing cluster on the nodes. You should remove the nodes from their clusters instead to keep the clusters working properly.


Additional info:

Error message from cluster setup:

# pcs cluster setup --name NewCluster virt-423 virt-424 virt-205
Error: virt-205: node is already in a cluster
Error: nodes availability check failed, use --force to override. WARNING: This will destroy existing cluster on the nodes. You should remove the nodes from their clusters instead to keep the clusters working properly.
Comment 2 Tomas Jelinek 2019-06-27 09:29:57 UTC 
In RHEL 7 it is not possible to enforce adding a node which is already part of another cluster. Considering we are in the late state of RHEL 7, this will not change. Since the "pcs cluster node add" command does not advice to use --force, there is no error message to be fixed in the same respect as error messages for "cluster setup" command in RHEL 7 and RHEL8 and "cluster node add" command in RHEL 8 have been fixed.

If you disagree, feel free to express your concerns and we will consider reopening the bz.
Note You need to log in before you can comment on or make changes to this bug.