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.

Description of problem:
pcs allows you to specify non-existent resource agent.


Version-Release number of selected component (if applicable):
pcs-0.9.26-9.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. pcs resource create dummystateful nonsense op monitor interval="5s"
2.
3.
  
Actual results:
Full list of resources:

 dummystateful	(ocf::heartbeat:nonsense):	Stopped 


Expected results:
pcs should catch this error while parsing the arguments. As it can already provide the list of resources and providers, it could filter the input against them to see if obvious mistake has not been made.

If error is detected, it should be printed (like "Specified resource is not valid, use pcs resource agents for a full list") and exit code should be non-zero.

Additional info:

https://github.com/feist/pcs/commit/f514ff7ef95366f074cf5d3a2dddd3a22871266a

Fixed upstream

Marking with docs_scoped - as this issue will not be documented in the Virtualization Administration Guide for RHEL 6.5

[root@ask-02 ~]# pcs -f temp.xml resource create dummystateful nonsense op monitor interval="5s"
Error: Unable to create resource 'nonsense', it is not installed on this system (use --force to override)
[root@ask-02 ~]# echo $?
1

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.

http://rhn.redhat.com/errata/RHBA-2013-1633.html