Ask Your Question

Revision history [back]

Forced to use answer field due to formatting leak in comments:- Files above /etc/neutron/plugin.ini && /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini are not configured properly.

1. /etc/neutron/plugin.ini should be soft link to /etc/neutron/plugins/ml2/ml2_conf.ini
lrwxrwxrwx. 1 root root       37 Jul 29 16:14 plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini 


[root@icehouse1 ~(keystone_admin)]# cat /etc/neutron/plugin.ini
[ml2]
type_drivers = vxlan
tenant_network_types = vxlan
mechanism_drivers =openvswitch
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
[ml2_type_vxlan]
vni_ranges =1001:2000
vxlan_group =239.1.1.2
[OVS]
local_ip=192.168.0.127
enable_tunneling=True
integration_bridge=br-int
tunnel_bridge=br-tun
[securitygroup]
enable_security_group = True
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[agent]
polling_interval=2
  1. Routing table clearly shows that that access to metadata has not been properly built . Sample

    [root@icehouse1 nova(keystone_admin)]# route -n

    Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 br-ex 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 enp5s1 169.254.0.0 0.0.0.0 255.255.0.0 U 1019 0 0 br-ex 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp5s1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

Forced to use answer field due to formatting leak in comments:- Files above /etc/neutron/plugin.ini && /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini are not configured properly.

1. /etc/neutron/plugin.ini should be soft link to /etc/neutron/plugins/ml2/ml2_conf.ini
lrwxrwxrwx. 1 root root       37 Jul 29 16:14 plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini 


[root@icehouse1 ~(keystone_admin)]# cat /etc/neutron/plugin.ini
[ml2]
type_drivers = vxlan
tenant_network_types = vxlan
mechanism_drivers =openvswitch
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
[ml2_type_vxlan]
vni_ranges =1001:2000
vxlan_group =239.1.1.2
[OVS]
local_ip=192.168.0.127
enable_tunneling=True
integration_bridge=br-int
tunnel_bridge=br-tun
[securitygroup]
enable_security_group = True
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[agent]
polling_interval=2
  1. Routing 2.Routing table clearly shows that that access to metadata has not been properly built . Sample

     [root@icehouse1 nova(keystone_admin)]# route -n

    -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 br-ex 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 enp5s1 169.254.0.0 0.0.0.0 255.255.0.0 U 1019 0 0 br-ex 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp5s1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

virbr0

Forced to use answer field due to formatting leak in comments:- Files above /etc/neutron/plugin.ini && /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini are not configured properly.

1. /etc/neutron/plugin.ini should be soft link to /etc/neutron/plugins/ml2/ml2_conf.ini
lrwxrwxrwx. 1 root root       37 Jul 29 16:14 plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini 


[root@icehouse1 ~(keystone_admin)]# cat /etc/neutron/plugin.ini
[ml2]
type_drivers = vxlan
tenant_network_types = vxlan
mechanism_drivers =openvswitch
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
[ml2_type_vxlan]
vni_ranges =1001:2000
vxlan_group =239.1.1.2
[OVS]
local_ip=192.168.0.127
enable_tunneling=True
integration_bridge=br-int
tunnel_bridge=br-tun
[securitygroup]
enable_security_group = True
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[agent]
polling_interval=2

Directory /etc/neutron ( network node )

[root@icehouse1 neutron(keystone_admin)]# ls -l
total 88
-rw-r--r--. 1 root root      193 Oct  6 16:22 api-paste.ini
-rw-r-----. 1 root neutron  3853 Oct  6 16:21 dhcp_agent.ini
-rw-r-----. 1 root neutron   208 Oct  6 16:22 fwaas_driver.ini
-rw-r-----. 1 root neutron  3431 Oct  6 16:21 l3_agent.ini
-rw-r-----. 1 root neutron  1400 Oct  3 03:25 lbaas_agent.ini
-rw-r-----. 1 root neutron  1863 Oct  6 16:22 metadata_agent.ini
-rw-r-----. 1 root neutron 19187 Oct  6 16:22 neutron.conf
-rw-r-----. 1 root neutron 17512 Oct  3 16:04 neutron.conf.rpmnew
lrwxrwxrwx. 1 root root       37 Oct  6 16:39 plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini
-rw-r--r--. 1 root root      452 Oct  6 16:37 plugin.orig
drwxr-xr-x. 4 root root       34 Oct  3 16:04 plugins
-rw-r-----. 1 root neutron  5858 Oct  3 03:25 policy.json
-rw-r--r--. 1 root root       85 Oct  3 16:04 release
-rw-r--r--. 1 root root     1216 Oct  3 03:25 rootwrap.conf

2.Routing table clearly shows that that access to metadata has not been properly built . Sample

 [root@icehouse1 nova(keystone_admin)]# route -n

    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
    169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
    169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
    169.254.0.0     0.0.0.0         255.255.0.0     U     1019   0        0 br-ex
    192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
    192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex
    192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0