<div dir="ltr">Adding a subject ^^<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 4, 2017 at 11:21 AM, Emilien Macchi <span dir="ltr"><<a href="mailto:emilien@redhat.com" target="_blank">emilien@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Aug 3, 2017 at 4:05 PM, Steve Baker <<a href="mailto:sbaker@redhat.com">sbaker@redhat.com</a>> wrote:<br>
> I would like to request a Feature Freeze Exemption (FFE) for the upper<br>
> constraints of the python-paunch library/tool in Pike.<br>
><br>
> <a href="https://review.openstack.org/#/c/490287/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/490287/</a><br>
><br>
> TripleO recently switched from using paunch as a library via heat-agents to<br>
> using the paunch CLI tool directly using ansible. This lead to a high impact<br>
> regression bug [1] where failed operations don't raise an error, fixed by<br>
> [2]. This leads to false positives in TripleO CI, and later deployment<br>
> failures which are more difficult to debug.<br>
><br>
> Release 1.5.0 contains a fix for this. It also contains the new "paunch<br>
> debug" command[3] which makes developing and debugging containers in TripleO<br>
> much easier. This feature has a low risk of causing regressions in paunch's<br>
> core function and is also desirable for the Pike release.<br>
<br>
</span>+1 from me.<br>
<span class=""><br>
> [1] <a href="https://bugs.launchpad.net/paunch/+bug/1707997" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>paunch/+bug/1707997</a><br>
> [2] <a href="https://review.openstack.org/#/c/489722/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/489722/</a><br>
> [3] <a href="https://review.openstack.org/#/c/476654/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/476654/</a><br>
><br>
</span>> ______________________________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Emilien Macchi<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>