uncapped mox3 from oslotest in stable/kilo pulls in conflicting pbr for kilo

Bug #1484967 reported by Matt Riedemann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslotest
Fix Released
Low
Matt Riedemann

Bug Description

Per kilo global-requirements, oslotest is capped right now to install 1.5.2:

https://github.com/openstack/requirements/blob/stable/kilo/global-requirements.txt#L236

oslotest>=1.5.1,<1.6.0 # Apache-2.0

And 1.5.2 requires pbr:

https://github.com/openstack/oslotest/blob/1.5.2/requirements.txt#L5

pbr!=0.7,<1.0,>=0.6

However, oslotest 1.5.2 requires uncapped mox3:

https://github.com/openstack/oslotest/blob/1.5.2/requirements.txt#L14

And the latest mox3 0.9.0 requires a newer pbr than what's capped in stable/kilo:

https://github.com/openstack/mox3/blob/0.9.0/requirements.txt#L4

pbr<2.0,>=1.3

So we need to cap mox3 in stable/kilo global-requirements so it doesn't pull in a version of pbr newer than what's in g-r for kilo.

Matt Riedemann (mriedem)
summary: - oslotest on stable/kilo requires pbr>=0.11
+ uncapped mox3 from oslotest in stable/kilo pulls in conflicting pbr for
+ kilo
no longer affects: oslotest
Revision history for this message
Matt Riedemann (mriedem) wrote :

This probably means capping mox3 in stable/kilo g-r at <=0.7.0 like in stable/juno because the 0.7.0 version had the proper cap on pbr:

pbr>=0.5.21,<1.0

Revision history for this message
Matt Riedemann (mriedem) wrote :
Changed in oslotest:
status: New → Confirmed
no longer affects: openstack-gate
Changed in oslotest:
importance: Undecided → Low
assignee: nobody → Matt Riedemann (mriedem)
Matt Riedemann (mriedem)
Changed in oslotest:
status: Confirmed → In Progress
Revision history for this message
Matt Riedemann (mriedem) wrote :

The g-r sync to oslotest in stable/kilo is here: https://review.openstack.org/#/c/213236/

We can release that as 1.5.3 now.

Revision history for this message
Matt Riedemann (mriedem) wrote :
Changed in oslotest:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.