Hide Forgot
There are currently two problems when we configure stonith via tripleo. A) https://bugs.launchpad.net/tripleo/+bug/1717531 parameter_defaults: EnableFencing: true FencingConfig: devices: - agent: fence_ipmilan host_mac: 00:92:bb:63:40:3d params: login: admin ipaddr: 192.168.24.1 ipport: 6230 passwd: password lanplus: 1 .... The deploy did not have stonith enabled: Cluster Properties: cluster-infrastructure: corosync cluster-name: tripleo_cluster dc-version: 1.1.16-12.13.el7.centos-94ff4df have-watchdog: false redis_REPL_INFO: overcloud-controller-0 stonith-enabled: false B) https://bugs.launchpad.net/tripleo/+bug/1717566 Stonith creation is racy and not all stonith resources get created. So the following might happen: Sep 15 09:43:51 localhost os-collect-config: "Notice: /Stage[main]/Tripleo::Fencing/Pacemaker::Stonith::Fence_ipmilan[00:92:bb:63:40:9f]/Exec[Create stonith-fence_ipmilan-0092bb63409f]/returns: executed successfully", Sep 15 09:43:51 localhost os-collect-config: "Notice: /Stage[main]/Tripleo::Fencing/Pacemaker::Stonith::Fence_ipmilan[00:92:bb:63:40:9f]/Exec[Add non-local constraint for stonith-fence_ipmilan-0092bb63409f]/returns: Error: Resource 'stonith-fence_ipmilan-0092bb63409f' does not exist" The reasons for this are the direct calls to the pcs command.
Reviews linked: A) https://bugs.launchpad.net/tripleo/+bug/1717531 https://review.openstack.org/504425 B) https://bugs.launchpad.net/tripleo/+bug/1717566 https://review.openstack.org/504931 https://review.openstack.org/504932
One more smaller patch is needed. gerrit @ openstack is down. will link here the review once it is up
Ok added last review. While this one (506326) is not essential for tripleo, it'd still be good to have
506326 merged, moving to POST again
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462