So in https://7f1d3bc811eac15dd3d0-a12e67e84744b622e6a13b507a2faa27.ssl.cf1.rackcdn.com/764782/2/check/tripleo-ci-centos-8-containers-multinode/b779d9b/logs/undercloud/home/zuul/overcloud_deploy.log we observe an odd thing. The same puppet code from the tripleo_ha_wrapper role gets invoked twice:
Dec 02 19:11:29 centos-8-ovh-gra1-0022018729 ansible-command[86253]: Invoked with _raw_params=puppet apply --detailed-exitcodes --summarize --color=false --modulepath '/etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules' --tags 'pacemaker::resource::bundle,pacemaker::property,pacemaker::resource::ip,pacemaker::resource::ocf,pacemaker::constraint::order,pacemaker::constraint::colocation' -e 'include ::tripleo::profile::base::pacemaker; include ::tripleo::profile::pacemaker::ovn_dbs_bundle'
and then shortly after
Dec 02 19:12:16 centos-8-ovh-gra1-0022018729 ansible-command[88379]: Invoked with _raw_params=puppet apply --detailed-exitcodes --summarize --color=false --modulepath '/etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules' --tags 'pacemaker::resource::bundle,pacemaker::property,pacemaker::resource::ip,pacemaker::resource::ocf,pacemaker::constraint::order,pacemaker::constraint::colocation' -e 'include ::tripleo::profile::base::pacemaker; include ::tripleo::profile::pacemaker::ovn_dbs_bundle'
This should not really happen because the ovn-dbs-pacemaker-puppet.yaml invokes the role only once and the role really calls puppet only once?
This then leads to the following failure:
Error: pcs -f /var/lib/pacemaker/cib/puppet-cib-backup20201202-88391-bdv7s2 resource create ip-192.168.24.7 IPaddr2 ip=192.168.24.7 cidr_netmask=32 meta resource-stickiness=INFINITY --disabled failed: Error: 'ip-192.168.24.7' already exists. Too many tries
If a command is disconnected while executing, ansible automatically retries. It might have happened in this case.