Fencing resources are not configured even though FencingConfig in fencing.yaml is written

Solution Verified - Updated -

Issue

  • FencingConfig is written in fencing.yaml file.

    parameter_defaults:
      EnableFencing: true
      FencingConfig:
        devices:
          - agent: fence_ipmilan
            host_mac: 00:00:00:00:00:aa
            params:
              ipaddr: 10.0.0.1
              lanplus: true
              login: admin
              passwd: ****
              pcmk_host_list: overcloud-controller-0
          - agent: fence_ipmilan
            host_mac: 00:00:00:00:00:bb
            params:
              ipaddr: 10.0.0.2
              lanplus: true
              login: admin
              passwd: ****
              pcmk_host_list: overcloud-controller-1
          - agent: fence_ipmilan
            host_mac: 00:00:00:00:00:cc
            params:
              ipaddr: 10.0.0.3
              lanplus: true
              login: admin
              passwd: ****
              pcmk_host_list: overcloud-controller-2
    
  • The aforementioned fencing.yaml is included in openstack overcloud deploy command.

    $ openstack overcloud deploy \
           :
      -e /home/stack/templates/fencing.yaml \
           :
    
  • However, no fencing resources are configured in the overcloud Pacemaker cluster.

    # pcs config
      :
    Stonith Devices:
    Fencing Levels:
      :
    
      ===> "Stonith Devices" and "Fencing Levels" are empty.
    

Environment

  • Red Hat OpenStack Platform 16.2
  • Red Hat OpenStack Platform 17.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content