Align requirements in all projects to global-requirements
Bug #1469045 reported by
Sebastian Kalinowski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Roman Prykhodchenko | ||
7.0.x |
Won't Fix
|
Undecided
|
Unassigned | ||
8.0.x |
Won't Fix
|
High
|
Roman Prykhodchenko | ||
Mitaka |
Fix Released
|
High
|
Roman Prykhodchenko |
Bug Description
Due to a lot of changes in openstack libraries and recent drop of 'oslo' namespace we have to introduce a lot of strange pining in requirementes of our projects.
We have to align with global-requirements both requirements in Python and in packages in our mirros.
Issue caused by this:
https:/
https:/
https:/
https:/
tags: | added: tech-debt |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
tags: | added: qa-agree-8.0 |
tags: | added: area-python |
tags: | added: blocked |
tags: | removed: blocked |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Roman Prykhodchenko (romcheg) |
Changed in fuel: | |
assignee: | Roman Prykhodchenko (romcheg) → Artem Roma (aroma-x) |
Changed in fuel: | |
assignee: | Artem Roma (aroma-x) → Roman Prykhodchenko (romcheg) |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
status: | In Progress → New |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
tags: | added: on-verification |
To post a comment you must log in.
We do not want to risk with updating packages right now and we also need a time to design a global solution for all our Python based modules. Moving to 8.0