Why doesn't neutron indicate an error has occurred through an exception? Is the port still valid even when this error has occurred?
** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1390336 Title: Libvirt: Raise wrong exception message when binding vif failed Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): In Progress Bug description: nova get an NovaException with wrong message due to wrong try to build an instance on compute node. 2014-11-07 14:40:54.446 ERROR nova.compute.manager [-] [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] Instance failed to spawn 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] Traceback (most recent call last): 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/compute/manager.py", line 2244, in _build_resources 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] yield resources 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/compute/manager.py", line 2114, in _build_and_run_instance 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] block_device_info=block_device_info) 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2597, in spawn 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] write_to_disk=True) 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4157, in _get_guest_xml 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] context) 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4018, in _get_guest_config 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] flavor, virt_type) 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] File "/opt/stack/nova/nova/virt/libvirt/vif.py", line 352, in get_config 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] _("Unexpected vif_type=%s") % vif_type) 2014-11-07 14:40:54.446 TRACE nova.compute.manager [instance: 9b56e64b-71b5-4598-b4df-45bb85b43ed6] NovaException: Unexpected vif_type=binding_failed To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1390336/+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