Comment 21 for bug 1671927

Revision history for this message
Scott Moser (smoser) wrote :

Jon,
That seems like a bug in your openstack. The point of 'latest' is that it is supposed to just be a copy of the "latest" (which would be 2015-10-15 for you). It should have the network-data.json file.

the code that generates that is in
https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py

From the openstack that I can get at, I see network_data.json available in 2015-10-15 (liberty) and later which aligns with what the code says should be there.

$ mount /dev/sr0 /mnt
$ ( cd /mnt && find * -type f )
ec2/2009-04-04/meta-data.json
ec2/latest/meta-data.json
openstack/2012-08-10/meta_data.json
openstack/2013-04-04/meta_data.json
openstack/2013-10-17/meta_data.json
openstack/2013-10-17/vendor_data.json
openstack/2015-10-15/meta_data.json
openstack/2015-10-15/network_data.json
openstack/2015-10-15/vendor_data.json
openstack/2016-06-30/meta_data.json
openstack/2016-06-30/network_data.json
openstack/2016-06-30/vendor_data.json
openstack/2016-10-06/meta_data.json
openstack/2016-10-06/network_data.json
openstack/2016-10-06/vendor_data.json
openstack/2016-10-06/vendor_data2.json
openstack/2017-02-22/meta_data.json
openstack/2017-02-22/network_data.json
openstack/2017-02-22/vendor_data.json
openstack/2017-02-22/vendor_data2.json
openstack/latest/meta_data.json
openstack/latest/network_data.json
openstack/latest/vendor_data.json
openstack/latest/vendor_data2.json