<html><head></head><body>From a quick glance at the logs my guess is that the issue is related to this stack trace in the l3 agent logs:<br>
<br>
<a href="http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657/logs/neutron/neutron-l3-agent.txt.gz?level=TRACE#_2017-10-29_23_11_15_146">http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657/logs/neutron/neutron-l3-agent.txt.gz?level=TRACE#_2017-10-29_23_11_15_146</a><br>
<br>
I'm not sure what's causing it to complain there. But, I'm on a plane right now (which is why this is a top post, sorry) so I can't really dig much more than that. I'll try to take a deeper look at things later when I'm on solid ground. (hopefully someone will beat me to it by then though) <br>
<br>
-Matt Treinish<br><br><div class="gmail_quote">On October 31, 2017 1:25:55 AM GMT+04:00, Mohammed Naser <mnaser@vexxhost.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi everyone,<br /><br />I'm looking for some help regarding an issue that we're having with<br />the Puppet OpenStack modules, we've had very inconsistent failures in<br />the Xenial with the following error:<br /><br /> <a href="http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657">http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657</a>/<br /> <a href="http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657/logs/testr_results.html.gz">http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ed5a657/logs/testr_results.html.gz</a><br /> Details: {u'message': u'Unable to associate floating IP<br /><a href="http://172.24.5.17">172.24.5.17</a> to fixed IP <a href="http://10.100.0.8">10.100.0.8</a> for instance<br />d265626a-77c1-4d2f-8260-46abe548293e. Error: Request to<br /><a href="https://127.0.0.1:9696/v2.0/floatingips/2e3fa334-d6ac-443c-b5ba-eeb521d6324c">https://127.0.0.1:9696/v2.0/floatingips/2e3fa334-d6ac-443c-b5ba-eeb521d6324c</a><br />timed out', u'code': 400}<br /><br />At this point, we're at a bit of a loss. I've tried my best in order<br />to find the root cause however we have not been able to do this. It<br />was persistent enough that we elected to go non-voting for our Xenial<br />gates, however, with no fix ahead of us, I feel like this is a waste<br />of resources and we need to either fix this or drop CI for Ubuntu. We<br />don't deploy on Ubuntu and most of the developers working on the<br />project don't either at this point, so we need a bit of resources.<br /><br />If you're a user of Puppet on Xenial, we need your help! Without any<br />resources going to fix this, we'd unfortunately have to drop support<br />for Ubuntu because of the lack of resources to maintain it (or<br />assistance). We (Puppet OpenStack team) would be more than happy to<br />work together to fix this so pop-in at #puppet-openstack or reply to<br />this email and let's get this issue fixed.<br /><br />Thanks,<br />Mohammed<br /><br /><hr /><br />OpenStack Development Mailing List (not for usage questions)<br />Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br /><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br /></pre></blockquote></div></body></html>