On Wed, Nov 09, 2016 at 10:18:25AM -0500, Mohammed Naser wrote:
:Have you tried turning off all agents, shut off all VMs on that node, destroy
br-int and be-tun, start neutron agents and try again?
Actually just figured out the problem and it's me :)
we have iptables rules on the hypervisor eth0
Have you tried turning off all agents, shut off all VMs on that node, destroy
br-int and be-tun, start neutron agents and try again?
Sent from my iPhone
> On Nov 9, 2016, at 9:51 AM, Jonathan D. Proulx wrote:
>
>
> Also I have restarted openvswitch-agent on both sides of the broken
> link and
Also I have restarted openvswitch-agent on both sides of the broken
link and it made no difference...
On Tue, Nov 08, 2016 at 05:43:27PM -0500, Jonathan Proulx wrote:
:
:I have an odd issue that seems to just be affecting one private
:network for one tenant, though I saw a similar thing on a diff
On Tue, Nov 08, 2016 at 06:27:34PM -0500, George Mihaiescu wrote:
:Hi Jonathan,
:
:The openvswitch-agent is out of sync on compute 4, try restarting it.
Nope.
Restarted the agent on 4 and when that failed also on 1 they still
can't talk.
I had previously migrated 4 to a new host to test that the
Hi Jonathan,
The openvswitch-agent is out of sync on compute 4, try restarting it.
> On Nov 8, 2016, at 17:43, Jonathan Proulx wrote:
>
>
> I have an odd issue that seems to just be affecting one private
> network for one tenant, though I saw a similar thing on a different
> project network
I have an odd issue that seems to just be affecting one private
network for one tenant, though I saw a similar thing on a different
project network recently which I 'fixed' by rebooting the hypervisor.
Since this has now (maybe) happened twice I figure I should try to
understand what it is.
Given
