Description of problem: ======================= I used packstack to install an openstack deployment (ML2, OVS+VXLAN) as follows: - 2 Compute nodes - 1 Neutron networker (L3, DHCP, Metadata) - 1 Openstack controller (all Openstack services including neutron-server) The Openstack controller is not a bridged node, thus packstack should not install a Neutron L2 agent on it and therefore a tunnel interface (VXLAN) is not needed. Hence, packstack should not expect to find an IP address configured with that interfece (in our case, eth3). The openstack services installed on the openstack controller are expected to communicate with the other nodes via the mgmt network (which in our case, routed via eth0). Version-Release number of selected component (if applicable): ============================================================= openstack-packstack-2013.2.1-0.28.dev989.el6ost.noarch How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. Use packstack with the following neutron configuration: CONFIG_NEUTRON_INSTALL=y CONFIG_NEUTRON_SERVER_HOST=192.168.160.29 CONFIG_NEUTRON_KS_PW=123456 CONFIG_NEUTRON_DB_PW=123456 CONFIG_NEUTRON_L3_HOSTS=192.168.160.27 CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex CONFIG_NEUTRON_DHCP_HOSTS=192.168.160.27 CONFIG_NEUTRON_LBAAS_HOSTS= CONFIG_NEUTRON_L2_PLUGIN=ml2 CONFIG_NEUTRON_METADATA_HOSTS=192.168.160.27 CONFIG_NEUTRON_METADATA_PW=123456 CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,vlan CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=openvswitch CONFIG_NEUTRON_ML2_FLAT_NETWORKS=* CONFIG_NEUTRON_ML2_VLAN_RANGES=ext_net:185:185 CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES=1:1000 CONFIG_NEUTRON_ML2_VXLAN_GROUP=224.0.0.1 CONFIG_NEUTRON_ML2_VNI_RANGES=3000:3100,2000:2100 CONFIG_NEUTRON_L2_AGENT=openvswitch CONFIG_NEUTRON_LB_TENANT_NETWORK_TYPE=local CONFIG_NEUTRON_LB_VLAN_RANGES= CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS= CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=vxlan CONFIG_NEUTRON_OVS_VLAN_RANGES=ext_net:185:186 CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=ext_net:br-ex CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:eth3.185,br-ex:eth3.186 CONFIG_NEUTRON_OVS_TUNNEL_RANGES=1:1000 CONFIG_NEUTRON_OVS_TUNNEL_IF=eth3 CONFIG_NEUTRON_OVS_VXLAN_UDP_PORT=4789 Openstack Controller: 192.168.160.29 Neutron Networker: 192.168.160.27 Compute Nodes: 192.168.160.21,192.168.160.25 Actual results: =============== Packstack expects a tunnel interface with IP address on a non-bridged node, the openstack controller. packstack fails with the following error: ERROR : Error appeared during Puppet run: 192.168.160.29_neutron.pp Error: Local ip for ovs agent must be set when tunneling is enabled at /var/tmp/packstack/f74cf0afb06a46b9acfbf9c4faa5d053/modules/neutron/manifests/agents/ovs.pp:30 on node <Openstack_Controllr_FQDN> You will find full trace in log /var/tmp/packstack/20140316-103744-CeaqEE/manifests/192.168.160.29_neutron.pp.log Please check log file /var/tmp/packstack/20140316-103744-CeaqEE/openstack-setup.log for more information Expected results: ================= Packstack should not expect a tunnel interface with IP address on a non-bridged node. Additional info: ================ As a workaround, configure an IP address on the tunnel interface for the OS controller node.
I appied the workarouned mentioned in Comment #0 and noticed that packstack needlessly installed a the Neutron L2 OVS agent on the Openstack controller node, which only contain the neutron-server service.
Expected to be fixed in the our next build