<p dir="ltr"><br>
On May 19, 2015 12:43 AM, "Andreas Jaeger" <<a href="mailto:aj@suse.com">aj@suse.com</a>> wrote:<br>
><br>
> On 05/19/2015 09:28 AM, Andreas Jaeger wrote:<br>
>><br>
>> On 05/19/2015 02:54 AM, Robert Collins wrote:<br>
>>><br>
>>> Hi, we had a gate outage today for a few hours.<br>
>>><br>
>>> <a href="http://pad.lv/1456376">http://pad.lv/1456376</a><br>
>>><br>
>>> The issue was an interaction between the existence of pbr 1.0, project<br>
>>> local requirements, hacking 0.10.1 and flake8 <2.4.1.<br>
>>><br>
>>> When flake8< 2.4.1 loads plugins (which hacking is) it uses<br>
>>> pkg_resources and calls load(), which checks requirements.<br>
>>><br>
>>> pbr in the pep8 jobs is installed by the project requirements.txt<br>
>>> files, which per global-requirements mostly now say ">=0.11, <2.0", so<br>
>>> pbr 1.0.0 was immediately installed once it was released.<br>
>>><br>
>>> hacking is installed from release, so hacking 0.10.1 was installed,<br>
>>> which has the constraint for pbr of <1.0 that we had prior to bumping<br>
>>> the releases in global-requirements. And so boom.<br>
>>><br>
>>> We've now released hacking 0.10.2, which contains only the updated pbr<br>
>>> constraint, and we don't expect any additional fallout from it.<br>
>>><br>
>>> Thanks Clark, Doug, Ian, Sean, and Joe for helping unwind, analyze and<br>
>>> fix this.<br>
>><br>
>><br>
>> There are some projects like ironic that pin an old hacking version and<br>
>> thus will not benefit from the new hacking release:<br>
>><br>
>> hacking>=0.9.2,<0.10<br>
>><br>
>> They need to update their hacking version [1],<br>
>><br>
>> Andreas<br>
>><br>
>> [1] <a href="https://review.openstack.org/184198">https://review.openstack.org/184198</a><br>
><br>
><br>
> Additional projects in the openstack namespace that might fail pep8 now due to the pinning of hacking:<br>
><br>
> castellan/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> congress/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> designate/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> heat-cfntools/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> heat-templates/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> ironic-python-agent/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> keystonemiddleware/test-requirements-py3.txt:hacking>=0.8.0,<0.9<br>
> kite/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> manila/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> murano-agent/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> os-apply-config/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> os-client-config/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> os-cloud-config/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> os-collect-config/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> os-refresh-config/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-cinderclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> python-congressclient/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-designateclient/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-glanceclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> python-heatclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> python-kiteclient/test-requirements.txt:hacking>=0.9.1,<0.10<br>
> python-manilaclient/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-muranoclient/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-swiftclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> python-troveclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> python-tuskarclient/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> python-zaqarclient/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> rally/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> swift-bench/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> swift/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> tripleo-image-elements/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> tripleo-puppet-elements/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> trove/test-requirements.txt:hacking>=0.8.0,<0.9<br>
> tuskar/test-requirements.txt:hacking>=0.9.2,<0.10<br>
> zaqar/test-requirements-py3.txt:hacking>=0.8.0,<0.9<br>
> zaqar/test-requirements.txt:hacking>=0.9.2,<0.10<br>
><br>
> I won't fix them myself. Note that the new hacking version indroduces new checks also might need to get fixed,<br>
></p>
<p dir="ltr">While I would like to see projects move off 0.9.x etc. I think the better option is to backport the fix to 0.9.x and 0.8.x as needed. </p>
<p dir="ltr">> Andreas<br>
><br>
> -- <br>
>  Andreas Jaeger aj@{<a href="http://suse.com">suse.com</a>,<a href="http://opensuse.org">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
>    GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton,<br>
>        HRB 21284 (AG Nürnberg)<br>
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126<br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><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>
</p>