<div dir="ltr"><span style="font-size:12.8px;font-weight:bold;white-space:nowrap">Dimitry Ushakov,</span><br><div><span style="font-size:12.8px;font-weight:bold;white-space:nowrap"><br></span></div><div><span style="font-size:12.8px;font-weight:bold;white-space:nowrap">Heat wait condition has a timeout, now the default for it is 6000 in our Heat template. I think we can change it to a reasonable value.</span></div><div><span style="font-size:12.8px;font-weight:bold;white-space:nowrap"><br></span></div><div><span style="font-size:12.8px;font-weight:bold;white-space:nowrap">Regards，</span></div><div><span style="font-size:12.8px;font-weight:bold;white-space:nowrap">wanghua</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 4, 2016 at 12:38 PM, Dimitry Ushakov <span dir="ltr"><<a href="mailto:dimitry.ushakov@rackspace.com" target="_blank">dimitry.ushakov@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>Eli,</div>
<div><br>
</div>
<div>I’m ok with removing that test but we’ll still have the real problem, which is the fact that heat hangs in heat_stack_create while /something/ in cloud init fails to complete. Currently, the theory is that etcdctl hangs, which leaves the entire stack
in the progress state [1]. Case in point, when bay create hangs, the test would still fail after about an hour [2] by giving up trying to create a bay. The last couple of days we’ve really been seeing a myriad of issues in the gates not related to Magnum,
from keystone version bump to apt-get failing (which caused the majority of check failures). I agree with the frustration but I’m afraid that just taking that test out won’t fix all our problems.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Dimitry </div>
<div><br>
</div>
<div>[1] <a href="https://bugs.launchpad.net/magnum/+bug/1541105" target="_blank">https://bugs.launchpad.net/magnum/+bug/1541105</a></div>
<div>[2] <a href="http://logs.openstack.org/65/272965/7/check/gate-functional-dsvm-magnum-api/4a35917/console.html#_2016-02-04_02_57_03_244" target="_blank">http://logs.openstack.org/65/272965/7/check/gate-functional-dsvm-magnum-api/4a35917/console.html#_2016-02-04_02_57_03_244</a></div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Eli Qiao <<a href="mailto:liyong.qiao@intel.com" target="_blank">liyong.qiao@intel.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, February 3, 2016 at 10:03 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [Magnum] Remove time costing case from gate-functional-dsvm-magnum-api<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000"><span class="">hello<br>
all, as you see that[1], gate failed to merge patch though gate since gate-functional-dsvm-magnum-api will cause timeout error and make job failed.<br>
by investigate cases in gate-functional-dsvm-magnum-api, these 2 are time costing.<br>
<br>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px"><span style="padding-left:22em;white-space:pre-wrap;display:block"><a name="21721523__2016-02-03_22_25_42_834" href="http://logs.openstack.org/94/260894/1/check/gate-functional-dsvm-magnum-api/f21b118/console.html#_2016-02-03_22_25_42_834" style="color:rgb(0,0,0);text-decoration:none" target="_blank">2016-02-03 22:25:42.834</a> | 2016-02-03 22:25:42.811 | magnum.tests.functional.api.v1.test_bay.BayTest.test_update_bay_name_for_existing_bay[negative] 1350.770
</span><span style="padding-left:22em;white-space:pre-wrap;display:block"><a name="21721523__2016-02-03_22_25_42_836" href="http://logs.openstack.org/94/260894/1/check/gate-functional-dsvm-magnum-api/f21b118/console.html#_2016-02-03_22_25_42_836" style="color:rgb(0,0,0);text-decoration:none" target="_blank">2016-02-03 22:25:42.836</a> | 2016-02-03 22:25:42.814 | magnum.tests.functional.api.v1.test_bay.BayTest.test_create_list_and_delete_bays[positive] 1300.981</span></pre>
<br>
I suggest to remove test_update_bay_name_for_exiting_bay as it can be covered by unit test.<br>
I proposed 2 patch to achieve that, please help to do review[2], let avoid reverify time to time.<br>
<br>
[1]<a href="https://review.openstack.org/#/c/260894/" target="_blank">https://review.openstack.org/#/c/260894/</a><br></span>
[2]<a href="https://review.openstack.org/276028" target="_blank">https://review.openstack.org/276028</a><a href="https://review.openstack.org/276029" target="_blank">https://review.openstack.org/276029</a><span class=""><br>
<pre cols="72">--
Best Regards, Eli(Li Yong)Qiao
Intel OTC China</pre>
</span></div>
</div>
</span>
</div>
<br>__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>