Public bug reported: Description of problem: PFs aren't showing up as available making it not possible to boot vms with PFs When I am trying to boot VM with Neutron port with vnic type - direct - physical there is an error. attached the error. The ENV is SRIOV 1 compute & 1 controller
Version-Release number of selected component (if applicable): python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch How reproducible: always Steps to Reproduce: 1.Deploy SRIOV ENV 2.Config the ENV to work with PF (no VFS configured ) 3.Create neutron port vnic type= direct physical 4.boot vm with neutrn port that created Actual results: VM is in ERROR state ** Affects: nova Importance: Undecided Status: New ** Attachment added: "pf nova boot" https://bugs.launchpad.net/bugs/1613610/+attachment/4721723/+files/pf%20nova%20boot -- 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/1613610 Title: SRIOV- PFs aren't showing up as available Status in OpenStack Compute (nova): New Bug description: Description of problem: PFs aren't showing up as available making it not possible to boot vms with PFs When I am trying to boot VM with Neutron port with vnic type - direct - physical there is an error. attached the error. The ENV is SRIOV 1 compute & 1 controller Version-Release number of selected component (if applicable): python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch How reproducible: always Steps to Reproduce: 1.Deploy SRIOV ENV 2.Config the ENV to work with PF (no VFS configured ) 3.Create neutron port vnic type= direct physical 4.boot vm with neutrn port that created Actual results: VM is in ERROR state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1613610/+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