Thanks. It's OpenStack ussuri, deployed via kolla-ansible
On Fri, Mar 18, 2022 at 10:06 PM Laurent Dumont laurentfdumont@gmail.com wrote:
That is weird.
- What version of Openstack are you running?
- How was it deployed?
On Fri, Mar 18, 2022 at 9:30 AM Ahmed Abdelhamid < ahmedabdelhamid1221@gmail.com> wrote:
Thanks, Laurent. I tried it for both CEPH-backed VMs and ones with local disk, still, the devices array is empty
Network data curl shows alright
{"links": [{"id": "tapa.....", "vif_id": "ae....", "type": "bridge", "mtu": 1500, "ethernet_mac_address": "fa:......."}], "networks": [{"id": "network0", "type": "ipv4_dhcp", "link": "tap.....
On Wed, Mar 16, 2022 at 6:39 PM Laurent Dumont laurentfdumont@gmail.com wrote:
Are you getting anything from the neutron endpoint?
http://169.254.169.254/openstack/2018-08-27/network_data.json
Can you provide an "openstack server show $server_id" of the VM? I wonder if it's a case of boot from a volume VM missing that data. It would not explain why the port is not there though.
On Tue, Mar 15, 2022 at 9:15 AM Ahmed Abdelhamid < ahmedabdelhamid1221@gmail.com> wrote:
Hi All,
I am running into a strange issue with the metadata service. Per metadata-service manual https://docs.openstack.org/nova/latest/user/metadata.html, the devices attached to a VM should be visible in
$ curl http://169.254.169.254/openstack/2018-08-27/meta_data.json
However, whenever i execute it from a VM , the devices array is empty and looks like this, any idea why ?
Thanks
{ "random_seed": "yu5ZnkqF2CqnDZVAfZgarG...", "availability_zone": "nova", "keys": [ { "data": "ssh-rsa AAAAB3NzaC1y...== Generated by Nova\n", "type": "ssh", "name": "mykey" } ], "hostname": "test.novalocal", "launch_index": 0, "meta": { "priority": "low", "role": "webserver" }, "devices": [ ], "project_id": "f7ac731cc11f40efbc03a9f9e1d1d21f", "public_keys": { "mykey": "ssh-rsa AAAAB3NzaC1y...== Generated by Nova\n" }, "name": "test"}