fencing .yaml not created properly in RHOSP

Solution Verified - Updated -

Issue

  • 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
parameter_defaults:
  EnableFencing: true
  FencingConfig:
    devices: []

Environment

  • 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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.