yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #79406
[Bug 1837927] Re: Missing mandatory path: http://169.254.169.254/openstack/2018-08-27/meta_data.json
Hi Orestes,
To work around this problem, you'll need to configure ds-identify[0] to
change its defaults. You should be able to do this by creating a file
named /etc/cloud/ds-identify.cfg and putting this in there:
datasource: Ec2
This will configure ds-identify to disable its usual platform-checking
behaviour and instead configure cloud-init to just attempt the Ec2 data
source.
As this is an issue with the OpenStack deployment you're using (rather
than a cloud-init bug), I'm going to close this out as Invalid. Please
feel free to follow up here, or drop in to #cloud-init on freenode for
any further assistance.
Thanks!
Dan
[0] https://git.launchpad.net/cloud-init/tree/tools/ds-identify
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1837927
Title:
Missing mandatory path:
http://169.254.169.254/openstack/2018-08-27/meta_data.json
Status in cloud-init:
Invalid
Bug description:
I'm running OpenStack Stein.
Cloud init from the bionic-cloud images it's not working correctly.
I'm launching instances with ubuntu-bionic 18.04 cloud and the
following message appears when reaching the openstack metadata server:
"[ 86.559374] cloud-init[843]: 2019-07-25 15:25:21,978 -
util.py[WARNING]: Missing mandatory path:
http://169.254.169.254/openstack/2018-08-27/meta_data.json"
Now, I can (without doing anything special) use ubuntu 14.04 cloud,
16.04 cloud, Centos7-cloud (all with different versions of cloud-init)
and everything works, but with 'Cloud-init v.
19.1-1-gbaa47854-0ubuntu1~16.04.1' on the bionic cloud images it does
not.
I have tried to use EC2 datasources, OpenStack datasources [1] and it
does not work. It connects to the metadata server and gets the
meta_data.json file but doesn't do much more. therefore I'm unable to
provision ssh keys, etc, with bionic-cloud. Attached is the full log
for one bionic-cloud-1804 instance.
1. https://cloudinit.readthedocs.io/en/latest/topics/datasources/openstack.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1837927/+subscriptions
References