Traceback is logged when the network node info is omitted in ml2_cisco.ini file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
When the Network node info is omitted in the ml2_conf.ini file, traceback is logged during stack.sh and when the first VM is launched.
Snippet of the local.conf:
#Nexus Switch
[ml2_mech_
qa5 = port-channel:
qa6 = port-channel:1
qa11 = port-channel:1
physnet = physnet1
ssh_port = 22
username = admin
password = CTO1234!
nve_src_intf = 2
NOTE: qa4 is the Network node connecting to port-channel 1
=======
2015-02-22 18:44:22.438 DEBUG neutron.
d port 2d4495da-
_nexus.py:651
2015-02-22 18:44:22.439 ERROR neutron.
port_level
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.439 TRACE neutron.
2015-02-22 18:44:22.440 WARNING neutron.
Cannot reproduce problem with Kilo, nova-manse version: 2015.2.