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 1099881 - move/ban of a stopped resource gives an error when node is not specified
Summary: move/ban of a stopped resource gives an error when node is not specified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-21 11:59 UTC by Tomas Jelinek
Modified: 2015-03-05 09:19 UTC (History)
5 users (show)

Fixed In Version: pcs-0.9.126-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: pcs does not detect that crm_resource is not able to ban stopped resource when node is not specified, because it is not possible to locate a node on which the resource is running. Consequence: crm_resource error message is presented to the user. The message is not very helpful because it is crm_resource specific. Fix: pcs detects that resource was not moved because crm_resource was not able to locate the resource node, and provides an explanatory error message. Result: User is informed about the cause of the error and how to avoid it.
Clone Of:
Environment:
Last Closed: 2015-03-05 09:19:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (962 bytes, patch)
2014-05-22 09:27 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0415 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2015-03-05 14:16:41 UTC

Description Tomas Jelinek 2014-05-21 11:59:31 UTC 
Description of problem:
Trying to move/ban a stopped resource without specifying the target node gives an error:
Error: error moving/banning/clearing resource
Resource 'dummy' not moved: active in 0 locations.
You can prevent 'dummy' from running on a specific location with: --ban --host <name>
Error performing operation: Invalid argument

Move/ban of a running resource works both with and without specifying the target node. Move/ban of a stopped resource with specifying the target node works too.


Version-Release number of selected component (if applicable):
pcs-0.9.115-32.el7


How reproducible:
always


Steps to Reproduce:
1. stop some resource e.g. 'pcs resource disable dummy'
2. try to move stopped resource without specifying the node: 'pcs resource move dummy'


Actual results:
Resource is not moved and an error message is presented to the user.
[root@localhost ~]# pcs resource move dummy
Error: error moving/banning/clearing resource
Resource 'dummy' not moved: active in 0 locations.
You can prevent 'dummy' from running on a specific location with: --ban --host <name>
Error performing operation: Invalid argument
[root@localhost pcs]# echo $?
1


Expected results:
Inform user that it is not possible to move/ban a stopped resource without specifying the target node.


Additional info:
pcs uses crm_resource for moving and baning the resources. crm_resource --move requires a target node specified otherwise it bans the resource on the node where the resource is currently running so the resource is moved to some other node. If the resource is stopped there is no node to put the ban on so crm_resource gives an error.
Comment 2 Tomas Jelinek 2014-05-22 09:27:03 UTC 
Created attachment 898299 [details]
proposed fix
Comment 3 Tomas Jelinek 2014-05-22 09:42:56 UTC 
Test:
1. create and stop a resource
[root@localhost ~]# pcs resource create dummy Dummy
[root@localhost ~]# pcs resource disable dummy

2. try to move the resource and check for error message
[root@localhost ~]# pcs resource move dummy
Error: You must specify a node when moving/banning a stopped resource

3. try to ban the resource and check for error message
[root@localhost ~]# pcs resource ban dummy
Error: You must specify a node when moving/banning a stopped resource
Comment 4 Tomas Jelinek 2014-09-11 09:08:54 UTC 
Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.115-32.el7.x86_64
[root@rh70-node1 ~]# pcs resource disable dummy
[root@rh70-node1 ~]# pcs resource move dummy
Error: error moving/banning/clearing resource
Resource 'dummy' not moved: active in 0 locations.
You can prevent 'dummy' from running on a specific location with: --ban --host <name>
Error performing operation: Invalid argument

[root@rh70-node1 ~]# echo $?
1


After Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.126-1.el7.x86_64
[root@rh70-node1 ~]# pcs resource create dummy Dummy
[root@rh70-node1 ~]# pcs resource disable dummy
[root@rh70-node1 ~]# pcs resource move dummy
Error: You must specify a node when moving/banning a stopped resource
[root@rh70-node1 ~]# echo $?
1
[root@rh70-node1 ~]# pcs resource ban dummy
Error: You must specify a node when moving/banning a stopped resource
[root@rh70-node1 ~]# echo $?
1
Comment 8 errata-xmlrpc 2015-03-05 09:19:34 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0415.html
Note You need to log in before you can comment on or make changes to this bug.