Please provide the package NVR for which the bug is seen:

pcs-0.12.0~a1-3.el10

How reproducible is this bug?:

always

Steps to reproduce

1. Try to use a resource or node id which is not configured in a cluster configuration when using resources or nodes filter in `pcs constraint location config` command

# pcs resource
NO resources configured


# pcs status nodes
Pacemaker Nodes:
 Online: r10-1.vm r10-2.vm
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:
Pacemaker Remote Nodes:
 Online:
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:

# pcs constraint location config resources missing-resource
# pcs constraint location config nodes missing-node

Expected results:

Warnings about non-existing resources or nodes.

Actual results:

No warnings.