Is this not the same issue worked around in the fix for
https://bugs.launchpad.net/cloud-init/+bug/1669875 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788487
Title:
OpenStack detection broken
FYI still seeing this on 18.5-21-g8ee294d5-0ubuntu1~16.04.1. Does anyone
have this working with just OpenStack and None datasources?
grep -i openstack /var/log/cloud-init*
/var/log/cloud-init.log:2019-03-12 16:48:22,086 - __init__.py[DEBUG]: Looking
for data source in: ['OpenStack', 'None'], via
@Scott,
DataSource OpenStack is still being skipped with cloud-init
18.4-0ubuntu1~16.04.2 even when explicitly setting:
datasource_list: [OpenStack, None]
Shouldn't it be probing for OpenStack metadata with this setting?
Thanks for any help. Generally I would prefer this to using an old
I appear to be running into the same issue described by Mark. Platform
is OpenStack using VMware (VC + ESXi). I first noticed this after
upgrading a template from Ubuntu 16.04.2 to 16.04.5 which bumped cloud-
init from 17.2-35 to 18.4-0. I got the EC2 warning as well :)
I'll be happy to check the
@Mark,
We did not intend to break your use case on 16.04.
Upstream has required strict identification of the platform for some time.
(bug 1669875 was filed ~ 18 months ago).
We do intend to support "explicit" datasource configuration via
setting datasource_list to have 1 entry (or 2 entries if
>From our experiments, doing 'b' is currently not possible. The first
thing the OpenStack datasource does is check the DMI data [1] and if it
does not match an expected platform, the metadata service is never
probed. This leaves cloud-init without any valid data source.
Ironically, the EC2
@Mark,
We believe the decision to limit cloud-init's "poll"ing of network based
metadata services is the right decision. That means that cloud-init will
only reach out to a metadata service if:
a.) it has positive identification that the metadata service will exist.
b.) it has been
Let me try to clarify the original issue. Commit
https://git.launchpad.net/cloud-
init/commit/?id=1efa8a0a030794cec68197100f31a856d0d264ab introduced a
mechanism where, for performance reasons, the OpenStack metadata service
is never queried if the host platform does not _look like_ OpenStack
from
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
