To Reproduce Steps to reproduce the behavior:

1. Install fence-agents-kubevirt package on all Controller VMs (manually or via Ansible playbook - both are working and rpm is there)
2. In openstack-config-generator.yaml file, Set the parameter enableFencing to true as in doc [1].
3. Delete current configgenerator CRD and recreate it for a new hash.
4. Update the new hash in openstack-deployment.yaml file and apply it.

Expected behavior

• Fencing config rendered properly.

Device Info (please complete the following information):

• • RHOSPdO 17.1.6
  • image-registry.openshift-image-registry.svc:5000/openstack/osp-director-operator-index:1.3.1-43
  • fence-agents-kubevirt-4.10.0-43.el9_2.12.x86_64

Bug impact

• Customer is unable to use the automation to  generate the fencing configuration.

Known workaround

• Configure fencing manually.

Additional context

• Similar to OSP-33530, but not related to `./`.
•  [1]https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html-single/deploying_an_overcloud_in_a_red_hat_openshift_container_platform_cluster_with_director_operator/index#proc_creating-ansible-playbooks-for-overcloud-configuration-with-the-openstackplaybookgenerator-CRD_OSPdO-overcloud-deploy