yahoo-eng-team team mailing list archive

[OpenStack Infra <1616442@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/377781
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1bcdc299ba8ffbf778fb1442cd8f9da59903ffdc
Submitter: Jenkins
Branch:    master

commit 1bcdc299ba8ffbf778fb1442cd8f9da59903ffdc
Author: Manjunath Patil <mpatil@xxxxxx>
Date:   Tue Sep 27 20:12:39 2016 +0530

    Allow the other nic to allocate VMs post PCI-PT VM creation.
    
    Let's say a compute node has got 2 network adapters
    (em1 and em2) with its correspondent VFs configured.
    If you start a VM with a direct-physical binding
    it will take one of these NICs.
    
    At that moment, SRIOV agent starts to show
    ERROR messages including the "device dictionary"
    completely empty.
    
    In consequence, you cannot allocate VMs with VFs
    even though there is still another NIC available.
    
    Change-Id: I8bf0dd41f900b69e32fcd416690c089dde7989b9
    Closes-Bug: #1616442


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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1616442

Title:
  SRIOV agent error when VM booted with direct-physical port

Status in neutron:
  Fix Released

Bug description:
  When assigning neutron port to PF (neutron port type - direct-physical )
  the vm is booted and active but there is errors in sriov agent log 
  attached  file with the errors 

  Version-Release number of selected component (if applicable):
  RHOS-10 
  [root@controller1 ~(keystone_admin)]# rpm -qa |grep neutron 
  python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
  openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
  python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  [root@controller1 ~(keystone_admin)]# rpm -qa |grep nova
  python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
  openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
  openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch

  How reproducible:

  
  Steps to Reproduce:
  1.deploy SRIOV setup and set PF functionality  you can use guide : 
  https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z0lTzx5itQ6WL0/edit#
  2.boot vm & assign it to PF 
  3.check in compute node sriov agent log

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616442/+subscriptions