[Rdo-list] [RESOLVED] Re: Launching a Nova instance results in "NovaException: Unexpected vif_type=binding_failed"

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 tenant: - Update ML2 config (specifically, update [agent] and [ovs] sections): ------ $ cat plugins/ml2/ml2_conf.ini | grep -v ^$ | grep -v ^# [ml2] type_drivers = gre tenant_network_types = gre mechanism_drivers = openvswitch [ml2_type_flat] [ml2_type_vlan] [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] [securitygroup] firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver enable_security_group = True [ovs] local_ip = 192.169.142.97 [agent] 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 missing. - Copy contents of `/etc/neutron/plugins/ml2/ml2_conf.ini` into `/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.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[1] for both Control and Compute nodes for reference. Hope this helps for someone who may hit similar issues. [1] http://kashyapc.fedorapeople.org/virt/openstack/rdo/IceHouse-Nova-Neutron... -- /kashyap