<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 5 August 2016 at 07:39, Brian Haley <span dir="ltr"><<a href="mailto:brian.haley@hpe.com" target="_blank">brian.haley@hpe.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">On 08/05/2016 08:59 AM, Sean Dague wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
On 08/04/2016 09:15 PM, Armando M. wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
So glad we are finally within the grasp of this!<br>
<br>
I posted [1], just to err on the side of caution and get the opportunity<br>
to see how other gate jobs for Neutron might be affected by this change.<br>
<br>
Are there any devstack-gate changes lined up too that we should be aware of?<br>
<br>
Cheers,<br>
Armando<br>
<br>
[1] <a href="https://review.openstack.org/#/c/351450/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/351450/</a><br>
</blockquote>
<br>
Nothing at this point. devstack-gate bypasses the service defaults in<br>
devstack, so it doesn't impact that at all. Over time we'll want to make<br>
neutron the default choice for all devstack-gate setups, and nova-net to<br>
be the exception. But that actually can all be fully orthoginal to this<br>
change.<br>
<br>
The experimental results don't quite look in yet, it looks like one test<br>
is failing on dvr (which is the one that tests for cross tenant<br>
connectivity) -<br>
<a href="http://logs.openstack.org/50/350750/5/experimental/gate-tempest-dsvm-neutron-dvr/4958140/" rel="noreferrer" target="_blank">http://logs.openstack.org/50/3<wbr>50750/5/experimental/gate-temp<wbr>est-dsvm-neutron-dvr/4958140/</a><br>
<br>
That test has been pretty twitchy during this patch series, and it's<br>
quite complex, so figuring out exactly why it's impacted here is a bit<br>
beyond me atm. I think we need to decide if that is going to get deeper<br>
inspection, we live with the fails, or we disable the test for now so we<br>
can move forward and get this out to everyone.<br>
</blockquote>
<br></span>
I took a quick look at this and can't reproduce it yet, here's what the test seems to do:<br>
<br>
1a. Create a network/subnet (<a href="http://10.100.0.0/28" rel="noreferrer" target="_blank">10.100.0.0/28</a>)<br>
b. attach a router interface to the subnet<br>
c. boot VM1 on the network<br>
<br>
2a. Create a network/subnet (<a href="http://10.100.0.16/28" rel="noreferrer" target="_blank">10.100.0.16/28</a>)<br>
b. do NOT attach a router interface to the subnet<br>
c. boot VM2 on the network<br>
<br>
3. Ssh to VM1 and ping VM2 - it should fail since there's no route to the network, but it succeeds<br>
<br>
The only place you should be able to ping that VM2 IP from is the dhcp namespace, which does work for me.<br>
<br>
So if you are seeing it be flaky it could the VM placement (same host vs different host) is impacting it? In the logs it showed the same hostId, but so did my test, so I don't have a good answer.</blockquote><div><br></div>Test <i>test_connectivity_between_vms_on_different_networks</i> failed on single node twice in a row. I think that VM placement may have nothing to do with it.<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class=""><font color="#888888"><br>
<br>
-Brian</font></span><div class=""><div class="h5"><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>