Excerpts from Chen CH Ji's message of 2018-04-11 21:09:29 +0800: > sorry, I didn't see any solution for following error found in [1] > I just rechecked the patch and is this kind of issue already fixed? > > ubuntu-xenial | Requirement for package eventlet : Requirement > (package=u'eventlet', location='', > specifiers='!=0.18.3,!=0.20.1,<0.21.0,>=0.18.2', markers=u'', comment=u'# > MIT', extras=frozenset([])) does not match openstack/requirements value : > set([Requirement(package='eventlet', location='', > specifiers='!=0.18.3,!=0.20.1,>=0.18.2', markers='', comment='# MIT', > extras=frozenset([]))])
The error message is correct. The requirements specification does not match and needs to be fixed by removing the cap from eventlet. Doug > > [1] > logs.openstack.org/87/523387/32/check/requirements-check/408e28c/job-output.txt.gz > > Best Regards! > > Kevin (Chen) Ji 纪 晨 > > Engineer, zVM Development, CSTL > Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com > Phone: +86-10-82451493 > Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, > Beijing 100193, PRC > > > > From: Doug Hellmann <d...@doughellmann.com> > To: openstack-dev <openstack-dev@lists.openstack.org> > Date: 04/11/2018 08:56 PM > Subject: Re: [openstack-dev] [all][requirements] uncapping eventlet > > Excerpts from IWAMOTO Toshihiro's message of 2018-04-11 18:19:02 +0900: > > On Mon, 09 Apr 2018 22:58:28 +0900, > > Doug Hellmann wrote: > > > > > > Excerpts from Tony Breeds's message of 2018-04-09 13:39:30 +1000: > > > > On Fri, Apr 06, 2018 at 09:41:07AM -0700, Clark Boylan wrote: > > > > > > > > > My understanding of our use of upper constraints was that this > should > > > > > (almost) always be the case for (almost) all dependencies. We > should > > > > > rely on constraints instead of requirements caps. Capping libs like > > > > > pbr or eventlet and any other that is in use globally is incredibly > > > > > difficult to work with when you want to uncap it because you have > to > > > > > coordinate globally. Instead if using constraints you just bump the > > > > > constraint and are done. > > > > > > > > Part of the reason that we have the caps it to prevent the tools that > > > > auto-generate the constraints syncs from considering these versions > and > > > > then depending on the requirements team to strip that from the bot > > > > change before committing (assuming it passes CI). > > > > > > > > Once the work Doug's doing is complete we could consider tweaking the > > > > tools to use a different mechanism, but that's only part of the > reason > > > > for the caps in g-r. > > > > > > > > Yours Tony. > > > > > > Now that projects don't have to match the global requirements list > > > entries exactly we should be able to remove caps from within the > > > projects and keep caps in the global list for cases like this where we > > > know we frequently encounter breaking changes in new releases. The > > > changes to support that were part of > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_c_555402_&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=y9YWvP5nDDQCyw3QGNWGvQS-CVeHBeXA9rfHaLf3JpQ&s=P99Z7BlpiP8Sg9_5Ku4JMW_tJWXARpd2ldSvFFlFBpU&e= > > > > > As eventlet has been uncapped in g-r, requirements-check is > > complaining on unrelated project-local requirement changes. > > I'm not quite sure but doesn't seem to be a intended behavior. > > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__logs.openstack.org_57_451257_16_check_requirements-2Dcheck_c32ee69_job-2Doutput.txt.gz&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=y9YWvP5nDDQCyw3QGNWGvQS-CVeHBeXA9rfHaLf3JpQ&s=6uHgERcFttsqFakjBTrjvKZhk5n-tZO-e0QMd7zj0nc&e= > > > > > This error is related to the change in > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_c_560050_&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=y9YWvP5nDDQCyw3QGNWGvQS-CVeHBeXA9rfHaLf3JpQ&s=1hIA6J9OfM1mhcTDq89NkGmoAQi_fDfhel7q5dgcwIA&e= > which applies the matching > rules to all requirements settings any time any requirements-related > file is touched. The change was made because we are less in-sync than we > thought and because we're allowing "bad" settings to stay in place. > > To correct the problem in the log you linked to, remove the cap from > eventlet in neutron. > > Doug > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev