GRE tunnels not created on fresh newton install

Bug #1630645 reported by Liam Young
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron-openvswitch (Juju Charms Collection)
Invalid
Critical
Liam Young

Bug Description

Running the specs/full_stack/next_deploy/newton mojo spec on xenial results in guests being unable to contact the gateway in 9/10 tests.

The issues shows itself as mojo being unable to ping the guest but digging into further shows the guest does not receive metadata or a dhcp address. Looking on the compute nodes and gateway node there are no gre tunnels being created. By default the cloud has L2 population enabled meaning that the gre tunnels *should* be created on demand.

Restarting neutron-openvswitch-agent on the compute and gateway nodes appears to fix the issue.

Liam Young (gnuoy)
Changed in neutron-openvswitch (Juju Charms Collection):
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Liam Young (gnuoy)
milestone: none → 16.10
Revision history for this message
Liam Young (gnuoy) wrote :

It seems a restart of neutron-openvswitch-agent on the gateway node is sufficient to fix the issue.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

Was this resolved by using a larger instance for neutron-gateway?

Revision history for this message
Liam Young (gnuoy) wrote :

Yes, it was. The issue was insufficient memory on the gateway instance.

Changed in neutron-openvswitch (Juju Charms Collection):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.