yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #33133
[Bug 1458968] [NEW] stable/juno unit tests blocked: ContextualVersionConflict: (oslo.i18n 1.3.1 (/home/jenkins/workspace/periodic-glance-python27-juno/.tox/py27/lib/python2.7/site-packages), Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
Public bug reported:
stable/juno unit tests are failing on (multiple) dependency conflicts.
Reproducible outside the gate simply running the py27 or py26 tox env
locally:
Tests in glance.tests.unit.test_opts fail with:
ContextualVersionConflict: (oslo.i18n 1.3.1 (/home/jenkins/workspace
/periodic-glance-python27-juno/.tox/py27/lib/python2.7/site-packages),
Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
This isn't affecting stable/juno tempest runs of this stuff since devstack sets up libraries directly from tip of the stable branches, where requirements have been updated to avoid this. Those fixes haven't been pushed out via releases to pypi, which is what the unit tests rely on.
There are two paths of conflict
glance (stable/juno) (keystonemiddleware>=1.0.0,<1.4.0)
-> keystonemiddleware (1.3.1) (pycadf>=0.6.0)
-> pycadf (0.9.0)
-> CONFLICT oslo.config>=1.9.3 # Apache-2.0
-> CONFLICT oslo.i18n>=1.5.0 # Apache-2.0
As per GR, we should be getting pycadf>=0.6.0,!=0.6.2,<0.7.0, but keystomemiddleware's uncapped dep is pulling in the newer.
https://review.openstack.org/#/c/173123/ resolves the issue by adding the proper stable/juno caps to keystonemiddleware stable/juno, but it looks like those changes need to be released as keystonemiddlware 1.3.2
** Affects: glance
Importance: Undecided
Status: New
** Affects: keystonemiddleware
Importance: Undecided
Status: New
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Summary changed:
- stable/juno unit tests wedged: ContextualVersionConflict: (oslo.i18n 1.3.1 (/home/jenkins/workspace/periodic-glance-python27-juno/.tox/py27/lib/python2.7/site-packages), Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
+ stable/juno unit tests blocked: ContextualVersionConflict: (oslo.i18n 1.3.1 (/home/jenkins/workspace/periodic-glance-python27-juno/.tox/py27/lib/python2.7/site-packages), Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1458968
Title:
stable/juno unit tests blocked: ContextualVersionConflict: (oslo.i18n
1.3.1 (/home/jenkins/workspace/periodic-glance-
python27-juno/.tox/py27/lib/python2.7/site-packages),
Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in OpenStack Identity (Keystone) Middleware:
New
Bug description:
stable/juno unit tests are failing on (multiple) dependency conflicts.
Reproducible outside the gate simply running the py27 or py26 tox env
locally:
Tests in glance.tests.unit.test_opts fail with:
ContextualVersionConflict: (oslo.i18n 1.3.1 (/home/jenkins/workspace
/periodic-glance-python27-juno/.tox/py27/lib/python2.7/site-packages),
Requirement.parse('oslo.i18n>=1.5.0'), set(['oslo.utils', 'pycadf']))
This isn't affecting stable/juno tempest runs of this stuff since devstack sets up libraries directly from tip of the stable branches, where requirements have been updated to avoid this. Those fixes haven't been pushed out via releases to pypi, which is what the unit tests rely on.
There are two paths of conflict
glance (stable/juno) (keystonemiddleware>=1.0.0,<1.4.0)
-> keystonemiddleware (1.3.1) (pycadf>=0.6.0)
-> pycadf (0.9.0)
-> CONFLICT oslo.config>=1.9.3 # Apache-2.0
-> CONFLICT oslo.i18n>=1.5.0 # Apache-2.0
As per GR, we should be getting pycadf>=0.6.0,!=0.6.2,<0.7.0, but keystomemiddleware's uncapped dep is pulling in the newer.
https://review.openstack.org/#/c/173123/ resolves the issue by adding the proper stable/juno caps to keystonemiddleware stable/juno, but it looks like those changes need to be released as keystonemiddlware 1.3.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1458968/+subscriptions
Follow ups
References