stonith resources in a single node cluster are always stopped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-pacemaker |
Fix Released
|
Undecided
|
Michele Baldessari |
Bug Description
On single node clusters puppet stonith should not create the location constraint to avoid the same host, otherwise the stonith resource will always be stopped:
Online: [ overcloud-
RemoteOnline: [ overcloud-
GuestOnline: [ galera-
Full list of resources:
overcloud-
Docker container: rabbitmq-bundle [192.168.
rabbitmq-
Docker container: galera-bundle [192.168.
galera-bundle-0 (ocf::heartbeat
Docker container: redis-bundle [192.168.
redis-bundle-0 (ocf::heartbeat
ip-192.168.24.10 (ocf::heartbeat
ip-10.0.0.101 (ocf::heartbeat
ip-172.17.1.14 (ocf::heartbeat
ip-172.17.1.12 (ocf::heartbeat
ip-172.17.3.18 (ocf::heartbeat
ip-172.17.4.14 (ocf::heartbeat
Docker container: haproxy-bundle [192.168.
haproxy-
stonith-
Clone Set: compute-
Stopped: [ overcloud-
nova-evacuate (ocf::openstack
stonith-
stonith-
Changed in puppet-pacemaker: | |
assignee: | nobody → Michele Baldessari (michele) |
This was actually fixed via I95d11d85d61bdd c6d8600f576801a 42af79a6652