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.
+++ This bug was initially created as a clone of Bug #2168155 +++
Description of problem:
When creating meta attributes for clones, keyword 'meta' is currently not used according to the documentation. However, it is not forbidden and user can obtain different results when creating a cloned resource in one step vs. when creating a resource and then clone it:
# pcs resource create d1 ocf:pacemaker:Dummy clone meta globally-unique=True
# pcs resource create d2 ocf:pacemaker:Dummy
# pcs resource clone d2 meta globally-unique=True
# pcs resource config
...
Clone: d1-clone
Resource: d1 (class=ocf provider=pacemaker type=Dummy)
Meta Attributes: d1-meta_attributes
globally-unique=True
...
Clone: d2-clone
Meta Attributes: d2-clone-meta_attributes
globally-unique=True
Resource: d2 (class=ocf provider=pacemaker type=Dummy)
...
Actual results:
Specifying 'meta' keyword after 'clone' when creating a cloned resource will create a resource primitive meta attribute whereas cloning the original resource with the same parameters will create a clone meta attribute.
Expected results:
The behavior should be consistent. If using keyword 'meta' is not any longer supported for creating clone meta attributes it should be forbidden or an alternative solution should be found to make the usage intuitive.
The problem here is, that `meta` has been always silently ignored in this command. We cannot just drop it all of a sudden. Doing so would break backward compatibility. The best we can do now is deprecate it a drop in the next major release. Since RHEL 9 is already released, we cannot drop it there. Considering that and the current phase of RHEL 8 life cycle, there is little to no point in addressing this in RHEL 8.