Upstream code uses
'numa_node': fields.IntegerField(nullable=True),
So this extra_info['numa_node'] must be a RHEL specific fork, so closing this
as invalid.
** Changed in: nova
Status: New => Invalid
--
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/1432905
Title:
Launching an instance fails when using a port with vnic_type=direct
Status in OpenStack Compute (Nova):
Invalid
Bug description:
After Launching an instance with a port with vnic_type=direct the
instance fails to start.
In the nova compute log I see:
2015-03-16 17:51:34.432 3313 TRACE nova.compute.manager ValueError: Field
`extra_info["numa_node"]' cannot be None
Version
=====
openstack-nova-compute-2014.2.2-18.el7ost.noarch
python-nova-2014.2.2-18.el7ost.noarch
openstack-nova-common-2014.2.2-18.el7ost.noarch
How to Reproduce
===============
# neutron port-create tenant1-net1 --binding:vnic-type direct
# nova boot --flavor m1.small --image rhel7 --nic port-id=<port-id> vm1
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1432905/+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
