Ask Your Question

Revision history [back]

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX or process running on port 9697, then run :- $ ps -ef | grep XXXX

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX or of process running on port 9697, then run :- $ ps -ef | grep XXXX

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

You wrote in question :-

sudo netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      13385/python

I would expect 13385 to be a PID of nova-api. On my Controller:-

[root@juno1 ~(keystone_admin)]# netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1646/python         
[root@juno1 ~(keystone_admin)]# ps -ef | grep 1646
nova      1646     1  0 08:42 ?        00:00:42 /usr/bin/python /usr/bin/nova-api
nova      3907  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      3908  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4008  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4009  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4075  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4076  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
root     32351  6546  0 10:37 pts/0    00:00:00 grep --color=auto 1646

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

You wrote in question :-

sudo netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      13385/python

I would expect 13385 to be a PID of nova-api. On my Controller:-

[root@juno1 ~(keystone_admin)]# netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1646/python         
[root@juno1 ~(keystone_admin)]# ps -ef | grep 1646
nova      1646     1  0 08:42 ?        00:00:42 /usr/bin/python /usr/bin/nova-api
nova      3907  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      3908  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4008  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4009  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4075  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4076  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
root     32351  6546  0 10:37 pts/0    00:00:00 grep --color=auto 1646

In my case RegionOne is in meta_data.ini

[root@juno1 ~(keystone_admin)]# keystone endpoint-list | grep RegionOne
| 066def1e55d74dd08730128053066df8 | RegionOne |           http://192.168.1.127:8774/v3          |           http://192.168.1.127:8774/v3          |        http://192.168.1.127:8774/v3        | b10170c2aa3c4ac5b6f2ef54a8e2e28f |
| 0e3c276843df427baac7fa28c21b4258 | RegionOne |            http://192.168.1.127:8080            |            http://192.168.1.127:8080            |         http://192.168.1.127:8080          | d28acbf47420467ab54e4e5677eaed8c |
| 34fa6b909c5646b48d2d387c622321e2 | RegionOne |    http://192.168.1.127:8776/v2/%(tenant_id)s   |    http://192.168.1.127:8776/v2/%(tenant_id)s   | http://192.168.1.127:8776/v2/%(tenant_id)s | 26624d1bafd14c7dbc0b19f019075264 |
| 5b2ad7ee3b9e46cb8ac58e41a507c211 | RegionOne |    http://192.168.1.127:8774/v2/%(tenant_id)s   |    http://192.168.1.127:8774/v2/%(tenant_id)s   | http://192.168.1.127:8774/v2/%(tenant_id)s | 613e434a682c44c5b2a0c8f67e7e8370 |
| 721b99d8907341049e7dcdb500fe4bc2 | RegionOne |     http://192.168.1.127:8773/services/Cloud    |     http://192.168.1.127:8773/services/Cloud    |  http://192.168.1.127:8773/services/Admin  | 96c7a62b70d04280bdb50b432820799a |
| 7277a0e2af754dc0b2fed7628953a118 | RegionOne | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s |         http://192.168.1.127:8080/         | a7e63c6eb99c491abf25999b63413059 |
| 85dd71016dc94070adc958c88237eefa | RegionOne |          http://192.168.1.127:5000/v2.0         |          http://192.168.1.127:5000/v2.0         |      http://192.168.1.127:35357/v2.0       | bfb9b914ac2c4c24adfa052dac05dea6 |
| 934b25fcb3a24901afa731ff50fd069e | RegionOne |    http://192.168.1.127:8776/v1/%(tenant_id)s   |    http://192.168.1.127:8776/v1/%(tenant_id)s   | http://192.168.1.127:8776/v1/%(tenant_id)s | b806d07a34cd471098c2d4bc13a0d1af |
| 9478e253adc64d96a775191d56e28258 | RegionOne |            http://192.168.1.127:9696/           |            http://192.168.1.127:9696/           |         http://192.168.1.127:9696/         | 8d53153adc5645788a0fa8276bc28367 |
| e5d4f2e6acd04c69ba00bf1ecdbf5b92 | RegionOne |            http://192.168.1.127:9292            |            http://192.168.1.127:9292            |         http://192.168.1.127:9292          | f1f1c1e36d704ed7b5bdab563c2ba29e |
| f99d4ebbb48743ddadd801e1f2783c62 | RegionOne |            http://192.168.1.127:8777            |            http://192.168.1.127:8777            |         http://192.168.1.127:8777          | 74036b3e507445049a041c475075ebed |

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

You wrote in question :-

sudo netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      13385/python

I would expect 13385 to be a PID of nova-api. On my Controller:-

[root@juno1 ~(keystone_admin)]# netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1646/python         
[root@juno1 ~(keystone_admin)]# ps -ef | grep 1646
nova      1646     1  0 08:42 ?        00:00:42 /usr/bin/python /usr/bin/nova-api
nova      3907  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      3908  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4008  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4009  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4075  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4076  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
root     32351  6546  0 10:37 pts/0    00:00:00 grep --color=auto 1646

In my case RegionOne is in meta_data.ini

[root@juno1 ~(keystone_admin)]# keystone endpoint-list | grep RegionOne
| 066def1e55d74dd08730128053066df8 | RegionOne |           http://192.168.1.127:8774/v3          |           http://192.168.1.127:8774/v3          |        http://192.168.1.127:8774/v3        | b10170c2aa3c4ac5b6f2ef54a8e2e28f |
| 0e3c276843df427baac7fa28c21b4258 | RegionOne |            http://192.168.1.127:8080            |            http://192.168.1.127:8080            |         http://192.168.1.127:8080          | d28acbf47420467ab54e4e5677eaed8c |
| 34fa6b909c5646b48d2d387c622321e2 | RegionOne |    http://192.168.1.127:8776/v2/%(tenant_id)s   |    http://192.168.1.127:8776/v2/%(tenant_id)s   | http://192.168.1.127:8776/v2/%(tenant_id)s | 26624d1bafd14c7dbc0b19f019075264 |
| 5b2ad7ee3b9e46cb8ac58e41a507c211 | RegionOne |    http://192.168.1.127:8774/v2/%(tenant_id)s   |    http://192.168.1.127:8774/v2/%(tenant_id)s   | http://192.168.1.127:8774/v2/%(tenant_id)s | 613e434a682c44c5b2a0c8f67e7e8370 |
| 721b99d8907341049e7dcdb500fe4bc2 | RegionOne |     http://192.168.1.127:8773/services/Cloud    |     http://192.168.1.127:8773/services/Cloud    |  http://192.168.1.127:8773/services/Admin  | 96c7a62b70d04280bdb50b432820799a |
| 7277a0e2af754dc0b2fed7628953a118 | RegionOne | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s |         http://192.168.1.127:8080/         | a7e63c6eb99c491abf25999b63413059 |
| 85dd71016dc94070adc958c88237eefa | RegionOne |          http://192.168.1.127:5000/v2.0         |          http://192.168.1.127:5000/v2.0         |      http://192.168.1.127:35357/v2.0       | bfb9b914ac2c4c24adfa052dac05dea6 |
| 934b25fcb3a24901afa731ff50fd069e | RegionOne |    http://192.168.1.127:8776/v1/%(tenant_id)s   |    http://192.168.1.127:8776/v1/%(tenant_id)s   | http://192.168.1.127:8776/v1/%(tenant_id)s | b806d07a34cd471098c2d4bc13a0d1af |
| 9478e253adc64d96a775191d56e28258 | RegionOne |            http://192.168.1.127:9696/           |            http://192.168.1.127:9696/           |         http://192.168.1.127:9696/         | 8d53153adc5645788a0fa8276bc28367 |
| e5d4f2e6acd04c69ba00bf1ecdbf5b92 | RegionOne |            http://192.168.1.127:9292            |            http://192.168.1.127:9292            |         http://192.168.1.127:9292          | f1f1c1e36d704ed7b5bdab563c2ba29e |
| f99d4ebbb48743ddadd801e1f2783c62 | RegionOne |            http://192.168.1.127:8777            |            http://192.168.1.127:8777            |         http://192.168.1.127:8777          | 74036b3e507445049a041c475075ebed |

Your ml2_conf.ini

ml2_conf.ini: 
[ml2] type_drivers = local,flat 
mechanism_drivers = openvswitch 
[ml2_type_flat] 
flat_networks = External 
[ovs] integration_bridge = br-int 
enable_tunneling = False 
local_ip = 10.1.12.2 
network_vlan_ranges = External 
bridge_mappings = External:br-ex 
[securitygroup] enable_security_group

I believe it cannot work with Neutron L3 layer. IT should be ML2 &OVS &(VXLAN or GRE or VLAN) setup.
View configs for VXLAN,GRE,VLAN beloow :
http://bderzhavets.blogspot.com/2014/07/rdo-setup-two-real-node_29.html (VXLAN)
http://bderzhavets.blogspot.com/2014/06/rdo-setup-two-real-node.html (GRE)
http://bderzhavets.blogspot.com/2014/06/rdo-icehouse-setup-two-node.html (VLAN)

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

You wrote in question :-

sudo netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      13385/python

I would expect 13385 to be a PID of nova-api. On my Controller:-

[root@juno1 ~(keystone_admin)]# netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1646/python         
[root@juno1 ~(keystone_admin)]# ps -ef | grep 1646
nova      1646     1  0 08:42 ?        00:00:42 /usr/bin/python /usr/bin/nova-api
nova      3907  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      3908  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4008  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4009  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4075  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4076  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
root     32351  6546  0 10:37 pts/0    00:00:00 grep --color=auto 1646

In my case RegionOne is in meta_data.ini

[root@juno1 ~(keystone_admin)]# keystone endpoint-list | grep RegionOne
| 066def1e55d74dd08730128053066df8 | RegionOne |           http://192.168.1.127:8774/v3          |           http://192.168.1.127:8774/v3          |        http://192.168.1.127:8774/v3        | b10170c2aa3c4ac5b6f2ef54a8e2e28f |
| 0e3c276843df427baac7fa28c21b4258 | RegionOne |            http://192.168.1.127:8080            |            http://192.168.1.127:8080            |         http://192.168.1.127:8080          | d28acbf47420467ab54e4e5677eaed8c |
| 34fa6b909c5646b48d2d387c622321e2 | RegionOne |    http://192.168.1.127:8776/v2/%(tenant_id)s   |    http://192.168.1.127:8776/v2/%(tenant_id)s   | http://192.168.1.127:8776/v2/%(tenant_id)s | 26624d1bafd14c7dbc0b19f019075264 |
| 5b2ad7ee3b9e46cb8ac58e41a507c211 | RegionOne |    http://192.168.1.127:8774/v2/%(tenant_id)s   |    http://192.168.1.127:8774/v2/%(tenant_id)s   | http://192.168.1.127:8774/v2/%(tenant_id)s | 613e434a682c44c5b2a0c8f67e7e8370 |
| 721b99d8907341049e7dcdb500fe4bc2 | RegionOne |     http://192.168.1.127:8773/services/Cloud    |     http://192.168.1.127:8773/services/Cloud    |  http://192.168.1.127:8773/services/Admin  | 96c7a62b70d04280bdb50b432820799a |
| 7277a0e2af754dc0b2fed7628953a118 | RegionOne | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s |         http://192.168.1.127:8080/         | a7e63c6eb99c491abf25999b63413059 |
| 85dd71016dc94070adc958c88237eefa | RegionOne |          http://192.168.1.127:5000/v2.0         |          http://192.168.1.127:5000/v2.0         |      http://192.168.1.127:35357/v2.0       | bfb9b914ac2c4c24adfa052dac05dea6 |
| 934b25fcb3a24901afa731ff50fd069e | RegionOne |    http://192.168.1.127:8776/v1/%(tenant_id)s   |    http://192.168.1.127:8776/v1/%(tenant_id)s   | http://192.168.1.127:8776/v1/%(tenant_id)s | b806d07a34cd471098c2d4bc13a0d1af |
| 9478e253adc64d96a775191d56e28258 | RegionOne |            http://192.168.1.127:9696/           |            http://192.168.1.127:9696/           |         http://192.168.1.127:9696/         | 8d53153adc5645788a0fa8276bc28367 |
| e5d4f2e6acd04c69ba00bf1ecdbf5b92 | RegionOne |            http://192.168.1.127:9292            |            http://192.168.1.127:9292            |         http://192.168.1.127:9292          | f1f1c1e36d704ed7b5bdab563c2ba29e |
| f99d4ebbb48743ddadd801e1f2783c62 | RegionOne |            http://192.168.1.127:8777            |            http://192.168.1.127:8777            |         http://192.168.1.127:8777          | 74036b3e507445049a041c475075ebed |

Your ml2_conf.ini

ml2_conf.ini: 
[ml2] type_drivers = local,flat 
mechanism_drivers = openvswitch 
[ml2_type_flat] 
flat_networks = External 
[ovs] integration_bridge = br-int 
enable_tunneling = False 
local_ip = 10.1.12.2 
network_vlan_ranges = External 
bridge_mappings = External:br-ex 
[securitygroup] enable_security_group

I believe it cannot work with Neutron L3 layer. IT should be ML2 &OVS ML2&OVS &(VXLAN or GRE or VLAN) setup.
View ml2 configs for VXLAN,GRE,VLAN beloow bellow :
http://bderzhavets.blogspot.com/2014/07/rdo-setup-two-real-node_29.html (VXLAN)
http://bderzhavets.blogspot.com/2014/06/rdo-setup-two-real-node.html (GRE)
http://bderzhavets.blogspot.com/2014/06/rdo-icehouse-setup-two-node.html (VLAN)

Forced to use answer field due to formatting options:-
Please , view a sample on Network Node :-
[root@juno1 ~(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     1006   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

On Compute Node

[root@juno2 ~]# 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 enp2s0
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
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 enp2s0

You are missing routes to 169.254.0.0 and hence your access to nova-metadata server is broken Please run:

$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a iptables -S -t nat | grep 169.254
$ ip netns exec qrouter-cd88cf9f-753e-4941-8234-9edcd9b2363a netstat -anpt

If it gives you PID XXXX of process running on port 9697, then run :- $ ps -ef | grep XXXX

You wrote in question :-

sudo netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      13385/python

I would expect 13385 to be a PID of nova-api. On my Controller:-

[root@juno1 ~(keystone_admin)]# netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1646/python         
[root@juno1 ~(keystone_admin)]# ps -ef | grep 1646
nova      1646     1  0 08:42 ?        00:00:42 /usr/bin/python /usr/bin/nova-api
nova      3907  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      3908  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4008  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4009  1646  0 08:43 ?        00:00:03 /usr/bin/python /usr/bin/nova-api
nova      4075  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
nova      4076  1646  0 08:43 ?        00:00:00 /usr/bin/python /usr/bin/nova-api
root     32351  6546  0 10:37 pts/0    00:00:00 grep --color=auto 1646

In my case RegionOne is in meta_data.ini

[root@juno1 ~(keystone_admin)]# keystone endpoint-list | grep RegionOne
| 066def1e55d74dd08730128053066df8 | RegionOne |           http://192.168.1.127:8774/v3          |           http://192.168.1.127:8774/v3          |        http://192.168.1.127:8774/v3        | b10170c2aa3c4ac5b6f2ef54a8e2e28f |
| 0e3c276843df427baac7fa28c21b4258 | RegionOne |            http://192.168.1.127:8080            |            http://192.168.1.127:8080            |         http://192.168.1.127:8080          | d28acbf47420467ab54e4e5677eaed8c |
| 34fa6b909c5646b48d2d387c622321e2 | RegionOne |    http://192.168.1.127:8776/v2/%(tenant_id)s   |    http://192.168.1.127:8776/v2/%(tenant_id)s   | http://192.168.1.127:8776/v2/%(tenant_id)s | 26624d1bafd14c7dbc0b19f019075264 |
| 5b2ad7ee3b9e46cb8ac58e41a507c211 | RegionOne |    http://192.168.1.127:8774/v2/%(tenant_id)s   |    http://192.168.1.127:8774/v2/%(tenant_id)s   | http://192.168.1.127:8774/v2/%(tenant_id)s | 613e434a682c44c5b2a0c8f67e7e8370 |
| 721b99d8907341049e7dcdb500fe4bc2 | RegionOne |     http://192.168.1.127:8773/services/Cloud    |     http://192.168.1.127:8773/services/Cloud    |  http://192.168.1.127:8773/services/Admin  | 96c7a62b70d04280bdb50b432820799a |
| 7277a0e2af754dc0b2fed7628953a118 | RegionOne | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.127:8080/v1/AUTH_%(tenant_id)s |         http://192.168.1.127:8080/         | a7e63c6eb99c491abf25999b63413059 |
| 85dd71016dc94070adc958c88237eefa | RegionOne |          http://192.168.1.127:5000/v2.0         |          http://192.168.1.127:5000/v2.0         |      http://192.168.1.127:35357/v2.0       | bfb9b914ac2c4c24adfa052dac05dea6 |
| 934b25fcb3a24901afa731ff50fd069e | RegionOne |    http://192.168.1.127:8776/v1/%(tenant_id)s   |    http://192.168.1.127:8776/v1/%(tenant_id)s   | http://192.168.1.127:8776/v1/%(tenant_id)s | b806d07a34cd471098c2d4bc13a0d1af |
| 9478e253adc64d96a775191d56e28258 | RegionOne |            http://192.168.1.127:9696/           |            http://192.168.1.127:9696/           |         http://192.168.1.127:9696/         | 8d53153adc5645788a0fa8276bc28367 |
| e5d4f2e6acd04c69ba00bf1ecdbf5b92 | RegionOne |            http://192.168.1.127:9292            |            http://192.168.1.127:9292            |         http://192.168.1.127:9292          | f1f1c1e36d704ed7b5bdab563c2ba29e |
| f99d4ebbb48743ddadd801e1f2783c62 | RegionOne |            http://192.168.1.127:8777            |            http://192.168.1.127:8777            |         http://192.168.1.127:8777          | 74036b3e507445049a041c475075ebed |

Your ml2_conf.ini

ml2_conf.ini: 
[ml2] type_drivers = local,flat 
mechanism_drivers = openvswitch 
[ml2_type_flat] 
flat_networks = External 
[ovs] integration_bridge = br-int 
enable_tunneling = False 
local_ip = 10.1.12.2 
network_vlan_ranges = External 
bridge_mappings = External:br-ex 
[securitygroup] enable_security_group

I believe it cannot work with Neutron L3 layer. IT should be ML2&OVS &(VXLAN or GRE or VLAN) setup.
View ml2 configs for VXLAN,GRE,VLAN bellow :
http://bderzhavets.blogspot.com/2014/07/rdo-setup-two-real-node_29.html (VXLAN)
http://bderzhavets.blogspot.com/2014/06/rdo-setup-two-real-node.html (GRE)
http://bderzhavets.blogspot.com/2014/06/rdo-icehouse-setup-two-node.html (VLAN)

View https://developer.rackspace.com/blog/neutron-networking-simple-flat-network/

Getting Started / What is a flat network?

For those coming from previous Essex- or Folsom-based Rackspace Private Cloud installations, flat networking in Neutron resembles the Flat DHCP model in Nova networking. For those new to the game, a flat network is one in which all instances reside on the same network (which may also be shared by the hosts). No vlan tagging takes place, and Neutron handles the assignment of IPs to instances using DHCP. Therefore, it’s possible to use unmanaged SOHO network switches to build a simple Neutron-based cloud, since there’s no need to configure switchports.

View https://developer.rackspace.com/blog/neutron-networking-l3-agent/

Networking / Building a router in Neutron

With the L3 agent properly configured, it's now time to build a router in Neutron. 
The configuration will mirror that of the diagram below, and assume a tagged VLAN 
provider network of 192.168.100.0/22 exists