[stable/ocata] Latest oslo.i18n version conflicts with latest Babel version

Bug #1709190 reported by Daniel Park
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Global Requirements
Won't Fix
Medium
Unassigned

Bug Description

The latest version of oslo.i18n (3.17.0) and the latest version of Babel (2.4.0) are being installed based on the following stable/ocata global requirements:

Babel>=2.3.4 # BSD
oslo.i18n>=2.1.0 # Apache-2.0

However, oslo.i18n 3.17.0 pins against Babel 2.4.0:
https://github.com/openstack/oslo.i18n/blob/3.17.0/requirements.txt#L6

This causes a VersionConflict exception when attempting to run components like Keystone.

Suggested solutions:
1) Pin against Babel 2.4.0 in global requirements or
2) Pin oslo.i18n to version <= 3.15.0

Daniel Park (daniepar)
description: updated
Revision history for this message
Matthew Thode (prometheanfire) wrote :

current upper-constraints.txt

Babel===2.3.4
oslo.i18n===3.12.0

Those are considered what are stable and tested for stable/ocata.

Babel 2.4.0 was blacklisted

Babel 2.4.0 does not handle "-" in locale po files like "ko-KR". This is fixed now for the upcoming Babel 2.4.1 release.

it sounds like we need to backport that to ocata.

Changed in openstack-requirements:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Tony Breeds (o-tony) wrote :

oslo.i18n 3.17.0 is a pike library and shouldn't be used on ocata. While I understand the temptation to block it that's not a thing we can do as it causes cascading problems.

The correct solution is to install packages with version as listed in upper-constraints.txt.

I'd consider a backport of the block of 2.4.0 from pike to ocata but not to newton (as this isn't a critical or security related bug)

https://review.openstack.org/493751 I'm not convinced that's the right thing to do

Revision history for this message
Matthew Thode (prometheanfire) wrote :

@daniepar why are you trying to install those versions instead using upper-constraints.txt?

Revision history for this message
Daniel Park (daniepar) wrote :

@prometheanfire this was what I ended up with after installing Keystone stable/ocata:
https://github.com/openstack/keystone/blob/736149c0cd91e66121229ed9aea8ddc90ea2eb26/requirements.txt

Guess I'll need to include the upper-constraints.txt whenever installing an OpenStack component?

Revision history for this message
Matthew Thode (prometheanfire) wrote :

That would be best, and make sure it's from the right branch.

Changed in openstack-requirements:
status: Triaged → Won't Fix
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.