- Red Hat OpenStack Platform 13.0
- Stonith fails with below error because it was enabled and could not find any stonith devices to fence as defined by fencing.yaml
# crm_verify -L -V error: unpack_resources: Resource start-up disabled since no STONITH resources have been defined error: unpack_resources: Either configure some or disable STONITH with the stonith-enabled option error: unpack_resources: NOTE: Clusters with shared data need STONITH to ensure data integrity
$ cat /home/stack/templates/environments/fencing.yaml parameter_defaults: EnableFencing: true FencingConfig: devices: - agent: fence_ipmilan host_mac: 42:10:D4:E0:00:1A <==== Must be lower case params: ipaddr: 10.241.1.145 lanplus: true login: admin passwd: password pcmk_host_list: controller-0 privlvl: administrator - agent: fence_ipmilan host_mac: 42:10:D4:E0:00:23 params: ipaddr: 10.241.1.155 lanplus: true login: admin passwd: password pcmk_host_list: controller-1 privlvl: administrator - agent: fence_ipmilan host_mac: 42:10:D4:E0:00:2C params: ipaddr: 10.241.1.164 lanplus: true login: admin passwd: password pcmk_host_list: controller-2 privlvl: administrator
- The file fencing.yaml is used to define stonith resources.
- Generate fencing.yaml using below command
openstack overcloud generate fencing --ipmi-lanplus --ipmi-level administrator --output fencing.yaml instackenv.json
- Deploy overcloud again by passing fencing.yaml environment file.
- The MAC address must always be in
small alphabetsinstead of capitals for stonith resources to be created.
- Red Hat OpenStack Platform
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.