yahoo-eng-team team mailing list archive

[OpenStack Infra <1743458@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/533804
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d16d0d553b20fd45a83cf7c68bc477b97aece9a1
Submitter: Zuul
Branch:    master

commit d16d0d553b20fd45a83cf7c68bc477b97aece9a1
Author: Artom Lifshitz <alifshit@xxxxxxxxxx>
Date:   Mon Jan 15 15:36:40 2018 -0500

    Refactor _build_device_metadata
    
    This patch splits out interface and disk metadata generation into its
    own function each, in preparation for handling hostdev metadata
    generation in a subsequent patch. It also adds some debug logging.
    
    Related-bug: 1743458
    Change-Id: I318b9118c97d7bf2b61bc45698443e8d0255ff6f


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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):
  Fix Released

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