For future records, when you get this error it is basically an execution timeout. In this case the NetworkConfig executed, the systems become unavailable, and ansible just hangs. Eventually the mistral -> zaqar connection either ends or a blank response is sent and the json decode error is thrown because the response is empty. To trouble shoot, check the `openstack workflow execution list` and see if there is a 'failed' task. You would be able to to do an `openstack workflow execution show <id> -f yaml` to get the error. If you hit this, it will tell you to look in the ansible.log for the failure. If the last task executing is NetworkConfig then the situation described above occurred. You will need to hop on the system's console and troubleshoot the network config. The improvement here might be to try and improve the 'timeout' messaging by catching this and doing some improved error handling. In future versions we've cleaned up this condition by removing the mistral to zaqar interactions.
DF doesn't have baremetal servers. Checked with submitter and problem is no longer seen.
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483