Description of problem:
If an update of pcmk bundle resource is being triggered during overcloud redeploy with some bundle resource config change and that resource has some existing location constraints (such as galera, rabbit, redis, ...) then overcloud update fails on something which looks like:
    \"+ puppet apply --debug --verbose --detailed-exitcodes --summarize --color=false --modulepath /etc/puppet/modules:/opt/stack/puppet-modules:/usr/shar
    e/openstack-puppet/modules --tags file,file_line,concat,augeas,pacemaker::resource::bundle,pacemaker::property,pacemaker::resource::ocf,pacemaker::constraint:
    :order,pacemaker::constraint::colocation,rabbitmq_policy,rabbitmq_user,rabbitmq_ready -e 'include ::tripleo::profile::base::pacemaker;include ::tripleo::profi
    le::pacemaker::rabbitmq_bundle'\",
            \"Failed to get D-Bus connection: Operation not permitted\",
            \"Warning: Undefined variable 'deploy_config_name'; \",
            \"   (file & line not available)\",
            \"Error: duplicate constraint already exists, use --force to override\",
            \"  Constraint: location-rabbitmq-bundle\",
            \"    Rule: score=0  (id:location-rabbitmq-bundle-rule)\",
            \"      Expression: rabbitmq-role eq true  (id:location-rabbitmq-bundle-rule-expr)\",
            \"Error: constraint location rabbitmq-bundle rule resource-discovery=exclusive score=0 rabbitmq-role eq true returned error. This should never happen.\",
            \"Error: /Stage[main]/Tripleo::Profile::Pacemaker::Rabbitmq_bundle/Pacemaker::Resource::Ocf[rabbitmq]/Pcmk_resource[rabbitmq]/ensure: change from absent to present failed: constraint location rabbitmq-bundle rule resource-discovery=exclusive score=0 rabbitmq-role eq true returned error. This should never happen.\",

It seems as location constraint is not being deleted before creating it again within resource update procedure which fails .

Version-Release number of selected component (if applicable):
puppet-pacemaker-0.7.2-0.20180423212250.el7ost

How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP13
2. Redeploy with following configuration change:
parameter_defaults:
  RabbitHAQueues: 0
  ExtraConfig:
    pacemaker::resource::bundle::deep_compare: true
    pacemaker::resource::ip::deep_compare: true
    pacemaker::resource::ocf::deep_compare: true

Actual results:
Overcloud Update fails

Expected results:
Successful redeploy with config change of rabbitmq resource (Ha policy all to exact)

Additional info: