+++ 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.