<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 19 December 2017 at 22:23, Brian Haley <span dir="ltr"><<a href="mailto:haleyb.dev@gmail.com" target="_blank">haleyb.dev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 12/19/2017 04:00 PM, Ben Nemec wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
On 12/19/2017 02:43 PM, Brian Haley wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 12/19/2017 11:53 AM, Ben Nemec wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
The reboot is done (mostly...see below).<br>
<br>
On 12/18/2017 05:11 PM, Joe Talerico wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Ben - Can you provide some links to the ovs port exhaustion issue for<br>
some background?<br>
</blockquote>
<br>
I don't know if we ever had a bug opened, but there's some discussion of it in <a href="http://lists.openstack.org/pipermail/openstack-dev/2016-December/109182.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pip<wbr>ermail/openstack-dev/2016-Dece<wbr>mber/109182.html</a> I've also copied Derek since I believe he was the one who found it originally.<br>
<br>
The gist is that after about 3 months of tripleo-ci running in this cloud we start to hit errors creating instances because of problems creating OVS ports on the compute nodes. Sometimes we see a huge number of ports in general, other times we see a lot of ports that look like this:<br>
<br>
Port "qvod2cade14-7c"<br>
tag: 4095<br>
Interface "qvod2cade14-7c"<br>
<br>
Notably they all have a tag of 4095, which seems suspicious to me. I don't know whether it's actually an issue though.<br>
</blockquote>
<br>
Tag 4095 is for "dead" OVS ports, it's an unused VLAN tag in the agent.<br>
<br>
The 'qvo' here shows it's part of the VETH pair that os-vif created when it plugged in the VM (the other half is 'qvb'), and they're created so that iptables rules can be applied by neutron. It's part of the "old" way to do security groups with the OVSHybridIptablesFirewallDrive<wbr>r, and can eventually go away once the OVSFirewallDriver can be used everywhere (requires newer OVS and agent).<br>
<br>
I wonder if you can run the ovs_cleanup utility to clean some of these up?<br>
</blockquote>
<br>
As in neutron-ovs-cleanup? Doesn't that wipe out everything, including any ports that are still in use? Or is there a different tool I'm not aware of that can do more targeted cleanup?<br>
</blockquote>
<br></span>
Crap, I thought there was an option to just cleanup these dead devices, I should have read the code, it's either neutron ports (default) or all ports. Maybe that should be an option.</blockquote><div><br></div><div>iirc neutron-ovs-cleanup was being run following the reboot as part of a ExecStartPre= on one of the neutron services this is what essentially removed the ports for us.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
-Brian</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Oh, also worth noting that I don't think we have os-vif in this cloud because it's so old. There's no os-vif package installed anyway.<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-Brian<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I've had some offline discussions about getting someone on this cloud to debug the problem. Originally we decided not to pursue it since it's not hard to work around and we didn't want to disrupt the environment by trying to move to later OpenStack code (we're still back on Mitaka), but it was pointed out to me this time around that from a downstream perspective we have users on older code as well and it may be worth debugging to make sure they don't hit similar problems.<br>
<br>
To that end, I've left one compute node un-rebooted for debugging purposes. The downstream discussion is ongoing, but I'll update here if we find anything.<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
Joe<br>
<br>
On Mon, Dec 18, 2017 at 10:43 AM, Ben Nemec <<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
It's that magical time again. You know the one, when we reboot rh1 to avoid<br>
OVS port exhaustion. :-)<br>
<br>
If all goes well you won't even notice that this is happening, but there is<br>
the possibility that a few jobs will fail while the te-broker host is<br>
rebooted so I wanted to let everyone know. If you notice anything else<br>
hosted in rh1 is down (<a href="http://tripleo.org" rel="noreferrer" target="_blank">tripleo.org</a>, zuul-status, etc.) let me know. I have<br>
been known to forget to restart services after the reboot.<br>
<br>
I'll send a followup when I'm done.<br>
<br>
-Ben<br>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote></blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>