Ask Your Question
1

Devstack install works, then network dies after some time

asked 2017-02-28 13:55:40 -0500

dalexander gravatar image

updated 2017-02-28 14:02:36 -0500

I am able to get a master build of devstack to work (on Ubuntu 16) just fine, using Neutron networking as well.

The problem is it dies after some seemingly random amount of time. Meaning, I cannot ssh into the system, access the dahsboard etc. It's a VM, and I can open the console, and I can even ping/ssh OUT of the box, just not into it.

Anyone ever see this? Yesterday I had it running for a couple hours once. Today the same thing, after I reverted the snapshot and ran trhough the whole stack.sh again. But then it just becomes unresponsive later....

I tried "screen -r" and restarting various services, nothing works.

Strange...anyone see this behavior before and know how to get around it?

*EDIT:

I see from the console that the default route is gone? I tried to add it back, still nothing.

Before it fails:

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface

0.0.0.0 10.210.16.1 0.0.0.0 UG 0 0 0 br-ex

10.210.16.0 0.0.0.0 255.255.240.0 U 0 0 0 br-ex

192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

After a while the default route is gone:

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface

10.210.16.0 0.0.0.0 255.255.240.0 U 0 0 0 br-ex

192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-03-03 13:02:23 -0500

dalexander gravatar image

Well, in my situation, I was using some range of IP's in my local.conf that for some reason didn't agree with my network. So I reduced the floating range to just a small portion of my subnet like this and now it's stable for a couple days already:

Enable Neutron

ENABLED_SERVICES+=,q-svc,q-dhcp,q-meta,q-agt,q-l3

Neutron options

Q_USE_SECGROUP=True FLOATING_RANGE=10.210.23.250/29 FIXED_RANGE="10.0.0.0/24" Q_FLOATING_ALLOCATION_POOL=start=10.210.23.251,end=10.210.23.254 PUBLIC_NETWORK_GATEWAY="10.210.23.248" Q_L3_ENABLED=True PUBLIC_INTERFACE=ens192 Q_USE_PROVIDERNET_FOR_PUBLIC=True OVS_PHYSICAL_BRIDGE=br-ex PUBLIC_BRIDGE=br-ex OVS_BRIDGE_MAPPINGS=public:br-ex

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-02-28 13:55:40 -0500

Seen: 46 times

Last updated: Mar 03 '17