ebd5679d11
With this change we explicitely tell the stonith-fence_compute-fence-nova resource which pacemaker nodes it is allowed to fence. This is a good idea in general as it makes things more explicit and we do not rely on other pcmk mechanisms (stonith querying the list of nodes returned by the fence agent) to determine which nodes it is allowed to fence. Tested with this change and the stonith resource is correctly set: [root@controller-0 ~]# pcs stonith config stonith-fence_compute-fence-nova Resource: stonith-fence_compute-fence-nova (class=stonith type=fence_compute) Attributes: auth_url=https://overcloud.redhat.local:13000 domain=redhat.local login=admin passwd=foo pcmk_host_list=compute-0,compute-1 project_domain=Default record_only=1 region_name=regionOne tenant_name=admin user_domain=Default Meta Attrs: provides=unfencing Operations: monitor interval=60s (stonith-fence_compute-fence-nova-monitor-interval-60s) .... Change-Id: Ia9c328a51d7f5dab933b096dd7a0792f2df2210e (cherry picked from commit 781d197a342c6c3ee82f951483930f3d66673b4c)
Team and repository tags
puppet-tripleo
Lightweight composition layer for Puppet TripleO.
Contributing
- Free software: Apache License (2.0)
- Source: http://git.openstack.org/cgit/openstack/puppet-tripleo
- Bugs: http://bugs.launchpad.net/tripleo (tag: puppet)
- Documentation:
- TripleO: https://docs.openstack.org/tripleo-docs/latest/
- Testing with puppet: https://docs.openstack.org/puppet-openstack-guide/latest/contributor/testing.html
- Release Notes: https://docs.openstack.org/releasenotes/puppet-tripleo