This is one of some of the current issues with with novafullsatck (see T309929 also)
ERROR
Instances are unable to get accesses through ssh, timing out.
Workaround
Not known
SOME NOTES
The VMs time out when trying to get the metadata for cloud-init:
2022-06-03 23:46:47,649 - util.py[DEBUG]: Resolving URL: http://169.254.169.254 took 0.007 seconds
2022-06-03 23:46:47,650 - url_helper.py[DEBUG]: [0/1] open 'http://169.254.169.254/openstack' with {'url': 'http://169.254.169.254/openstack', 'allow_redirects': True, 'method': 'GET', 'timeout': 10.0, 'headers': {'User-Agent': 'Cloud-Init/20.4.1'}} configuration
2022-06-03 23:46:57,663 - url_helper.py[DEBUG]: Calling 'http://169.254.169.254/openstack' failed [10/-1s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Read timed out. (read timeout=10.0)]
2022-06-03 23:46:57,664 - DataSourceOpenStack.py[DEBUG]: Giving up on OpenStack md from ['http://169.254.169.254/openstack'] after 10 seconds
2022-06-03 23:46:57,664 - util.py[WARNING]: No active metadata service found
2022-06-03 23:46:57,665 - util.py[DEBUG]: No active metadata service found
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceOpenStack.py", line 145, in _get_data
results = self._crawl_metadata()
File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceOpenStack.py", line 181, in _crawl_metadata
raise sources.InvalidMetaDataException(
cloudinit.sources.InvalidMetaDataException: No active metadata service foundThat prevents the VM from getting a hostname, and in turn prevents puppet from running, failing to setup anything else.