This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2219554 - Improve documentation and error messages of `pcs resource move` command
Summary: Improve documentation and error messages of `pcs resource move` command
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 9.4
Assignee: Tomas Jelinek
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks: 2233763
TreeView+ depends on / blocked
 
Reported: 2023-07-04 09:39 UTC by Ondrej Mular
Modified: 2023-09-22 20:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Improve an error message when 'pcs resource move' command fails. Reason: Previously, it wasn't clear in which phase the command failed and what it left behind in the cluster configuration. Result: If the command left a move constraint behind, pcs explicitly points it out and provides a guidance on removing the constraint.
Clone Of:
: 2233763 (view as bug list)
Environment:
Last Closed: 2023-09-22 20:23:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs pcs issues 697 0 None closed Question : Specifications of pcs resource move. 2023-07-04 09:39:41 UTC
Red Hat Issue Tracker   RHEL-7719 0 None Migrated None 2023-09-22 20:24:00 UTC
Red Hat Issue Tracker RHELPLAN-161483 0 None None None 2023-07-04 09:41:59 UTC
Red Hat Issue Tracker RHELPLAN-161484 0 None None None 2023-07-04 09:41:53 UTC

Description Ondrej Mular 2023-07-04 09:39:42 UTC 
Documentation of `pcs resource move` command needs to better describe a case when command fails and a constraint used to move the resource is not removed by pcs afterwards. Error message produced by pcs in a such case may also be improved to suggest to use `pcs resource clear <resource> [<node>]` command in order to remove the constraint. However, the error message should be clear that removal of the constraint may cause the resource to move to another node.
Comment 2 Tomas Jelinek 2023-09-06 09:02:42 UTC 
Upstream patch: https://github.com/ClusterLabs/pcs/commit/0ba9d1c947c8e55954b49afd634493c39fee5e76

Test:
1) Have a cluster with several resources:
Full List of Resources:
  * xvm (stonith:fence_xvm):     Started rh92-node1
  * d1  (ocf:pacemaker:Dummy):   Started rh92-node2
  * d2  (ocf:pacemaker:Dummy):   Started rh92-node1
  * d3  (ocf:pacemaker:Dummy):   Started rh92-node2
  * d4  (ocf:pacemaker:Dummy):   Started rh92-node1
  * d5  (ocf:pacemaker:Dummy):   Started rh92-node2
  * d6  (ocf:pacemaker:Dummy):   Started rh92-node1

2) Run a command to move d6 to the other node:
pcs resource move d6

3) Wait for the command from step 2 print this:
Location constraint to move resource 'd6' has been created
Waiting for the cluster to apply configuration changes...

4) Immediately, before the command from step 2 ends, move other resources in the cluster:
pcs constraint location d5 prefers rh92-node2; pcs constraint location d4 prefers rh92-node2; pcs constraint location d3 prefers rh92-node2

5) The command from step 2 ends with an improved error message:
Error: Unable to ensure that moved resource 'd6' will stay on the same node after a constraint used for moving it is removed. The constraint to move the resource has not been removed from configuration. Consider removing it manually. Be aware that removing the constraint may cause resources to move to other nodes. Run 'pcs resource clear d6' to remove the constraint.
Comment 3 RHEL Program Management 2023-09-22 20:23:31 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 4 RHEL Program Management 2023-09-22 20:23:54 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.
Note You need to log in before you can comment on or make changes to this bug.