cloned resources are broken with pcmk2.x/pcs0.10

[Michele Baldessari]

pacemaker 2.0 and pcs 0.10 removed support for the option '--clone'. Now the syntax to use is 'clone' only (without the leading dashes)

This needs a backwards-compatible fix.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/660883

[Michele Baldessari (michele)]

https://review.opendev.org/660883

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/660883
Committed: https://git.openstack.org/cgit/openstack/puppet-pacemaker/commit/?id=c03a507462ffec2f053f2e56754b04560138412b
Submitter: Zuul
Branch: master

commit c03a507462ffec2f053f2e56754b04560138412b
Author: Michele Baldessari <email address hidden>
Date: Tue May 21 16:49:15 2019 +0200

    pcs 0.10 clone resources changed parameters

    pcs 0.10 changed syntax for clone resources. It does not use '--clone'
    as previously, but needs 'clone' instead. Tested on RHEL8 with pcmk2.0
    and pcs 0.10.0 and correctly got a cloned resource up and running with
    an existing puppet manifest:

     Clone Set: compute-unfence-trigger-clone [compute-unfence-trigger]
         Started: [ compute-0 compute-1 ]
         Stopped: [ controller-0 controller-1 controller-2 ]

    Closes-Bug: #1830162

    Change-Id: I63a0b5bde92c008467fe362b5374891a95f19184

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-pacemaker 0.8.0 release.