Comment 5 for bug 1837927

Thanks for the extra info! It looks to me a lot like your OpenStack deployment is misconfigured. In both xenial and bionic, the metadata service appears to advertise support for metadata version 2018-08-27, but http://169.254.169.254/openstack/2018-08-27/meta_data.json is apparently not returning anything. I would suggest that you talk to your administrator to address this issue.

The reason that this isn't a hard blocker on xenial is that in xenial, we will try every data source that cloud-init ships. If you read through the log, you can see that we actually end up using the Ec2 data source, which hits the OpenStack EC2 compatibility API.

On bionic, cloud-init only attempts to reach out to network endpoints for platforms that it has positively identified it is running on. In this case, cloud-init has correctly identified that this is an OpenStack instance, so it only runs the OpenStack data source (which fails, due to the broken nature of your cloud's metadata API).