Bug 2219554

Summary:	Improve documentation and error messages of `pcs resource move` command
Product:	Red Hat Enterprise Linux 9	Reporter:	Ondrej Mular <omular>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.3	CC:	cluster-maint, idevat, mlisik, mpospisi, nhostako, omular, tojeline
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	9.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:
Clones:	2233763 (view as bug list)		Environment:
Last Closed:	2023-09-22 20:23:54 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:
Bug Depends On:
Bug Blocks:	2233763

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.