OpenStack detection broken on VMware
Bug #1788487 reported by
Mark
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
The OpenStack data source in cloud-init 18.3 was updated to detect OpenStack systems before probing the metadata endpoint. This broke for several cloud platforms (e.g. LP: #1784685) and is also broken for VMware.
As can be seen in LP: #1669875 there is no way to discern OpenStack on VMware from DMI data. A way around this could be to generally add 'VMware Virtual Platform' to the list of valid DMI platform names (`VALID_
https:/
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
You should be able to specifically set the datasource in /etc/cloud/ cloud.cfg. d/*.cfg
with:
datasource_list: ['OpenStack', 'None']
I know this is not ideal, but in lieu of some mechanism for detecting that this platform provides an openstack metadata service on http:// 169.254. 169.254/ openstack it is currently the best option.
You mention "several cloud platforms" but list only vmware.
Can you give more details on other platforms?
Please also attach the output of 'cloud-init collect-logs' on any platform you see failure.
Thanks.