<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Jesse,<div><br></div><div>We have had success with 3.2.0-58 and OVS 1.10.2. We too have experienced kernel panics with stock OVS and 3.2.0-58</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>---</div><div>Joseph Breu</div><div>Deployment Engineer</div><div>Rackspace Private Cloud</div><div>210-312-3508</div></div></span></div></span></span>
</div>
<br><div><div>On Feb 11, 2014, at 10:20 AM, Simon Pasquier <<a href="mailto:simon.pasquier@bull.net">simon.pasquier@bull.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Jesse,<br><br>I've run into the same kernel panic you experienced [1] and openvswitch-1.4.6 didn't help either. I don't have the issue with kernel 3.2.0-56 so I'm sticking with that version.<br>I've no time to investigate further in the short term but I'll keep you posted.<br><br>HTH,<br><br>Simon<br><br>[1] <a href="https://bugs.launchpad.net/openstack-cisco/+bug/1260334">https://bugs.launchpad.net/openstack-cisco/+bug/1260334</a><br><br>On 09/02/2014 12:08, Jesse Pretorius wrote:<br><blockquote type="cite">Hi everyone,<br><br>We have a production cloud system running on Ubuntu 12.04 LTS with<br>Openstack Grizzly from the Ubuntu Cloud Archive. We're using the stock<br>Openvswitch from the Precise repo.<br><br>Current levels:<br>kernel 3.2.0-54<br>openvswitch 1.4.0-1ubuntu1.5<br>openstack 1:2013.1.4-0ubuntu1~cloud0<br><br>Recently I tried doing a dist-upgrade to kernel 3.2.0-58. After the<br>reboot everything seemed fine, then the quantum ovs agent started,<br>initiated the gre tunnels and the kernel panicked. Not good. As it turns<br>out, this has been picked up by others:<br><a href="https://bugs.launchpad.net/openstack-cisco/+bug/1260334">https://bugs.launchpad.net/openstack-cisco/+bug/1260334</a><br>https://bugs.launchpad.net/ubuntu/precise/+source/openvswitch/+bug/1262692<br><br>So, the simplest solution appeared to be to try updating to<br>openvswitch-1.4.6 from precise-proposed. I tried that (admittedly<br>keeping the kernel version static) on a network node and it borked again.<br><br>Alright, so perhaps I should just let sleeping dogs lie and leave the<br>software levels as they are. That'd be great except that as they are I'm<br>experiencing issues with port tagging not working properly for router<br>internal ports and dhcp service ports:<br>https://bugs.launchpad.net/neutron/+bug/1269795<br><br>So, I'd like to know from anyone still reading - what levels of kernel,<br>openvswitch and openvswitch-datapath-dkms do you have working perfectly<br>in production?<br><br>I'm aware of the potential performance issues with a sub-v1.11 ovs -<br>slow performance is a lesser issue for me right now, and we have other<br>protections against DOS attacks, I'm more concerned with having a stable<br>system that works as it's supposed to.<br><br>Ideally I'd like a combination of packages directly from Ubuntu Archive<br>and Cloud Archive - preferably no compilations from source or PPA's. I'm<br>happy to use some packages from Havana Cloud Archive if they come<br>recommended.<br><br>So far it looks to me like this may work:<br>kernel 3.11.0-12 - using linux-lts-saucy from Ubuntu Archive<br>openvswitch 1.10.2 - from Havana Cloud Archive<br>openvswitch-datapath-dkms 1.10.2 - from Havana Cloud Archive<br><br>Any thoughts, comments or anecdotes would be highly appreciated.<br><br><br>_______________________________________________<br>OpenStack-operators mailing list<br>OpenStack-operators@lists.openstack.org<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br><br></blockquote><br><br>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br></blockquote></div><br></div></body></html>