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.

From time to time users run into an issue that they want to rename a resource (group, clone) and there is no pcs command for it.
http://lists.clusterlabs.org/pipermail/users/2017-February/004946.html

This command would need to modify all references to the renamed resources as well.

Also we should consider stopping the resource before renaming and starting it afterwards. From pacemaker point of view a simple rename in CIB means the original resource was deleted and another one was created. That creates orphaned resources.

Maybe it makes sense for some other ids (eg. acl).

Another upstream requests for this feature:
http://lists.clusterlabs.org/pipermail/users/2017-April/005387.html
http://lists.clusterlabs.org/pipermail/users/2017-April/005450.html

(In reply to Tomas Jelinek from comment #0)
> Also we should consider stopping the resource before renaming and starting
> it afterwards. From pacemaker point of view a simple rename in CIB means the
> original resource was deleted and another one was created. That creates
> orphaned resources.

Better idea: allow renaming only stopped resources. Stopping a resource can take a long time (even hours for databases) and there is a risk of timeout or other failures. Renaming running resources could be allowed with --force.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.