We can finally close this thread out. Now that we are up and running on
2.0.0 and not crashing we have been able to resolve our remaining issues.
We are now successfully running an OpenStack environment and are able to
deploy instances successfully. Our remaining issue from yesterday was
solved whe
Okay, good news. I was able to get my br-tun interfaces back online and can
confirm that we are still not crashing. I still can't get my instances to
get IPs yet, but working to get that fixed next. Thank you.
On Thu, Jan 23, 2014 at 9:27 AM, Travis Wilson wrote:
> Okay, I may have spoken too so
Okay, I may have spoken too soon. On further investigation of my instances
not working issue I discovered this morning that after my upgrades
yesterday my br-tun instances had been removed from both my network and
compute nodes. I suspect that is why 1.9.3 and 2.0.0 didn't crash initially
for me. I
I didn't push too hard on 1.9.3 to be honest, but the initial instance
deployment worked and that was what had crashed on me consistently
previously so I kind of just called it good and then decided to go ahead
and move up to 2.0 since you said it had a larger rewrite of the tunneling
code. Probabl
Hmm, that's interesting. I'm glad that 1.9.3 fixed the problem
although I didn't see any changes from 1.9 that I would expect to
resolve this. However, 2.0 has a much simpler tunneling stack so I
would expect that to be more reliable.
On Wed, Jan 22, 2014 at 11:25 AM, Travis Wilson
wrote:
> Good
Good day again Jesse.
I wanted to provide you and the group with an update on our issue. We tried
several times to get a kdump out of the system but never were able to
successfully get that to work. Based on that we decided to take a look at
the newer versions of Open vSwitch as you had mentioned
Thanks, this is useful.
If you have the binary and can use gdb to find what line is causing the
problem based on the instruction pointer, that would be very helpful. I
agree that it seems unlikely that this is memory corruption.
On Fri, Jan 17, 2014 at 5:51 AM, Travis Wilson wrote:
> Good day.
>
On Fri, Jan 10, 2014 at 12:34 PM, Travis Wilson
wrote:
> Good day.
>
> We are new to OpenStack and Open vSwitch and have run into an issue
> where when deploying a VM instance either our Compute Node or Network
> Node consistently kernel panic. From what we can see on the screen
> when the panics
Good day.
We are new to OpenStack and Open vSwitch and have run into an issue
where when deploying a VM instance either our Compute Node or Network
Node consistently kernel panic. From what we can see on the screen
when the panics occur it appears that Open vSwitch components may be
involved but w
