Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1203182

Summary: Launching an instance fails when using a port with vnic_type=direct
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: openstack-novaAssignee: Nikola Dipanov <ndipanov>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0 (Juno)CC: berrange, dasmith, eglynn, kchamart, ndipanov, nyechiel, pbrady, sbauza, sferdjao, sgordon, slong, vromanso, yeylon
Target Milestone: z2Keywords: Regression, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2014.2.2-19.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-07 15:09:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Itzik Brown 2015-03-18 10:50:00 UTC 
Description of problem:
After Launching an instance with a port with vnic_type=direct the instance fails to start.

In compute log:
nova.compute.manager ValueError: Field `extra_info["numa_node"]' cannot be None

Version-Release number of selected component (if applicable):
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 reproducible:


Steps to Reproduce:
1. Create a port with vnic_type=direct
2. Launch an instance with the above port attached.
3. 

Actual results:
Instance fails to start.

Expected results:


Additional info:
Comment 4 Itzik Brown 2015-03-20 14:18:10 UTC 
Checked with openstack-nova-2014.2.2-19.el7ost.noarch
Comment 7 Summer Long 2015-03-23 23:55:57 UTC 
Thanks Nikola, I've set the requires_doc_text flag to '-'. For future bugs, you can do this yourself. thanks, Summer
Comment 9 errata-xmlrpc 2015-04-07 15:09:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0790.html