Public bug reported: Description ===========
When booting an instance with a PF passed through, device tags applied to the PF do not appear in the metadata. Steps to reproduce ================== Create a PF neutron port: $ neutron port-create sriov --binding:vnic-type direct-physical --name pf Boot a VM with that port: $ nova test-sriov_vf_2 [...] --nic port- id=88691de9-1a20-4f86-9931-e694786b5bdf,tag=ticky >From inside the guest, access the metadata: $ curl http://169.254.169.254/openstack/latest/meta_data.json Expected result =============== A device with role tag 'ticky' appears in the metadata. Actual result ============= No device with role tag 'ticky' in the metadata. Environment =========== 1. Exact version of OpenStack you are running. This was originally reported in Red Hat OpenStack 10 (Newton), but I believe the problem still exists on master. 2. Which hypervisor did you use? libvirt+kvm 3. Which networking type did you use? neutron ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1743458 Title: Device tagging does not work for PF passthrough Status in OpenStack Compute (nova): New Bug description: Description =========== When booting an instance with a PF passed through, device tags applied to the PF do not appear in the metadata. Steps to reproduce ================== Create a PF neutron port: $ neutron port-create sriov --binding:vnic-type direct-physical --name pf Boot a VM with that port: $ nova test-sriov_vf_2 [...] --nic port- id=88691de9-1a20-4f86-9931-e694786b5bdf,tag=ticky From inside the guest, access the metadata: $ curl http://169.254.169.254/openstack/latest/meta_data.json Expected result =============== A device with role tag 'ticky' appears in the metadata. Actual result ============= No device with role tag 'ticky' in the metadata. Environment =========== 1. Exact version of OpenStack you are running. This was originally reported in Red Hat OpenStack 10 (Newton), but I believe the problem still exists on master. 2. Which hypervisor did you use? libvirt+kvm 3. Which networking type did you use? neutron To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1743458/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp