Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
As it is possible to use clone id to "unclone" cloned resources, it might be useful (especially for a custom clone id which now can be set) to mention it in pcs help/man.
Version-Release number of selected component (if applicable):
pcs-0.10.8-1.el8
Actual results:
pcs help and man states:
pcs resource unclone <resource id | group id> [--wait[=n]]
Expected results:
pcs resource unclone <clone id | resource id | group id> [--wait[=n]]
Test:
[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-2.el8.x86_64
[root@r8-node-01 ~]# pcs resource unclone --help
Usage: pcs resource unclone...
unclone <clone id | resource id | group id> [--wait[=n]]
Remove the specified clone or the clone which contains the specified
group or resource (the resource or group will not be removed). If
--wait is specified, pcs will wait up to 'n' seconds for the operation
to finish (including stopping clone instances if appropriate) and then
return 0 on success or 1 on error. If 'n' is not specified it defaults
to 60 minutes.
From a man page:
unclone <clone id | resource id | group id> [--wait[=n]]
Remove the specified clone or the clone which contains
the specified group or resource (the resource or group
will not be removed). If --wait is specified, pcs will
wait up to 'n' seconds for the operation to finish
(including stopping clone instances if appropriate) and
then return 0 on success or 1 on error. If 'n' is not
specified it defaults to 60 minutes.
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 (Low: pcs security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:4142