fencing .yaml not created properly in RHOSP

Solution Verified - Updated -


  • Following official guide to generate the fencing.yaml file so that fencing on overcloud nodes can be configured using director but skeleton file is created without any content.
$ cat fencing.yaml
  EnableFencing: true
    devices: []


  • Red Hat OpenStack Platform 11
  • Red Hat OpenStack Platform 12
  • Red Hat OpenStack Platform 13

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