Description of problem: Unable to use ~/.config/openstack/clouds.yaml or /etc/openstack/clouds.yaml config files. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create fence_openstack fence device 2. 3. Actual results: Unable to set cloud to use in config files, and agent doesnt look for the config files. Expected results: Able to set cloud=<name> to use config from ~/.config/openstack/clouds.yaml or /etc/openstack/clouds.yaml (~/ takes precedent like it does for openstack cli). Additional info: https://github.com/ClusterLabs/fence-agents/pull/465 https://github.com/ClusterLabs/fence-agents/pull/466
Example clouds.yaml: [root@nodea ~]# cat .config/openstack/clouds.yaml clouds: rhelha-user: auth: auth_url: https://<IP>:13000/ project_name: projectname username: user password: pass user_domain_name: Default project_domain_name: Default region_name: regionOne verify: False
Setting ITM to 26 to get release+. Brandon, if we need a different ITM go ahead and change it.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (fence-agents bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:7981