On 02/26/2016 03:48 AM, Paul Carlton wrote:
Sean
Don't think unstack failed, when I manually create the device ( sudo ovs-vsctl
--no-wait -- --may-exist add-br br-ex) unstack.sh removes it.
sudo ip route show
default via 172.18.20.1 dev eth0
169.254.169.254 via 172.18.20.2 dev eth0
172.18.20.0/24 dev eth0 proto kernel scope link src 172.18.20.23
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Matt
config attached
So getting back to your original error:
$ sudo ip route replace 10.1.0.0/20 via 192.168.100.200
RTNETLINK answers: Network is unreachable
Looking at your local.conf:
FIXED_RANGE=10.1.0.0/20
FLOATING_RANGE=192.168.100.0/24
Q_FLOATING_ALLOCATION_POOL=start=192.168.100.200,end=192.168.100.254
PUBLIC_NETWORK_GATEWAY=192.168.100.1
PUBLIC_BRIDGE=br-ex
The 'ip route replace...' above is adding a route for the fixed IP range you've
specified for your private subnet via what should be the neutron router for the
network. That router was allocated .200 when it attached to the external
subnet, which is fine.
In order for this to work, the IP $PUBLIC_NETWORK_GATEWAY (192.168.100.1) needs
to have been configured on br-ex ($PUBLIC_BRIDGE) beforehand, since otherwise
the network will be unreachable. Does 'ip a s dev br-ex' show that IP?
It could be that some setting in your local.conf is causing some
mis-configuration, pasting 'neutron port-list' and 'neutron subnet-list' might
help track down what is wrong.
-Brian
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
