Description of problem: The fencing.yaml is generated properly, just some resource warnings are observed while generating the fencing.yaml file. ~~~ (undercloud) [stack@undercloud ~]$ openstack overcloud generate fencing --ipmi-lanplus --ipmi-level administrator --output fencing.yaml instackenv.json /usr/lib/python3.6/site-packages/osc_lib/shell.py:176: ResourceWarning: unclosed file <_io.TextIOWrapper name='fencing.yaml' mode='w' encoding='UTF-8'> ret_value = super(OpenStackShell, self).run_subcommand(argv) /usr/lib/python3.6/site-packages/osc_lib/shell.py:176: ResourceWarning: unclosed file <_io.TextIOWrapper name='instackenv.json' mode='r' encoding='UTF-8'> ret_value = super(OpenStackShell, self).run_subcommand(argv) sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.24.2', 45296), raddr=('192.168.24.2', 13000)> sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=9, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.24.2', 54104), raddr=('192.168.24.2', 13989)> ~~~ Version-Release number of selected component (if applicable): python3-openstackclient-3.18.0-0.20190312140834.6868499.el8ost.noarch
So the file warnings are fixed in the linked review. The SSL warnings look like they will be fixed via: https://bugs.launchpad.net/keystoneauth/+bug/1838704
I also confirm that via BZ https://bugzilla.redhat.com/show_bug.cgi?id=1733557 (and https://review.opendev.org/#/c/674139/) the SSL warnings are gone
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, 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-2020:0710