Dependency on un-versioned WebOb breaks other services in shared installation

Bug #950378 reported by Maru Newby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Melange
Invalid
Undecided
Unassigned

Bug Description

The WebOb dependency in tools/pip-requires does not include a version specifier, resulting in the latest version (>1.2) being installed. Unfortunately, most other OpenStack projects are only compatible with WebOb < 1.2, as they use deprecated features that raise DeprecationWarning exceptions in 1.2.

The webob dependency for melange should be explicitly set to 1.0.8, the version used by the other OpenStack projects.

Revision history for this message
Jason Kölker (jason-koelker) wrote :

But melange doesn't have bugs in it that cause it to not work with later versions. This is not a melange bug, this is an other project bug. If WebOb 1.0.8 is installed, then melange will work, if its another version, melange will work.

Changed in melange:
status: New → Invalid
Revision history for this message
Maru Newby (maru) wrote :

I fully intend to update all projects for WebOb >= 1.2 compatibility, and work on getting per-project venv installation in devstack.

In the meantime, it would seem prudent to specify WebOb==1.0.8 for melange to ensure that melange can be safely installed in devstack. Or do you not want people to be able to use melange with devstack?

Revision history for this message
Jason Kölker (jason-koelker) wrote :

Melange is installed as the last service in devstack for this reason. We have used devstack to successfully install and run a Nova+Quantum+Melange installation. What sequence of events lead to Melange being installed prior to the dependencies of the other projects?

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.