[Rdo-list] [RESOLVED] Re: Launching a Nova instance results in "NovaException: Unexpected vif_type=binding_failed"
kchamart at redhat.com
Wed May 14 17:45:41 UTC 2014
Ater a bit (lot) of debugging (thanks to Attila Fazekas), I was able to
boot a Nova instance and get it aquire DHCP lease.
A few things I did that have fixed the non-booting of a guest w/ user
- Update ML2 config (specifically, update [agent] and [ovs] sections):
$ cat plugins/ml2/ml2_conf.ini | grep -v ^$ | grep -v ^#
type_drivers = gre
tenant_network_types = gre
mechanism_drivers = openvswitch
tunnel_id_ranges = 1:1000
enable_security_group = True
local_ip = 188.8.131.52
tunnel_types = gre
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
This change brought in the 'br-tun' interface that I was previously
- Copy contents of `/etc/neutron/plugins/ml2/ml2_conf.ini`
(Thanks Attila Fazekas for this tip, he mentioned upstream Devstack
does this, not sure of the rationale).
- Use these config attributes in nova.conf:
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
vif_plugging_is_fatal = False
vif_plugging_timeout = 0
- Add "agent_down_time = 75" to [DEFAULT] section of neutron.conf and
"report_interval = 5" to [agent] section.
Finally, here are my Neutron and Nova configuration details for both
Control and Compute nodes for reference.
Hope this helps for someone who may hit similar issues.
More information about the dev