Bug 972055
Summary: | python-neutronclient requires python-cliff 1.3 | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Brent Eagles <beagles> | |
Component: | python-neutronclient | Assignee: | Jakub Ruzicka <jruzicka> | |
Status: | CLOSED WONTFIX | QA Contact: | Roey Dekel <rdekel> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 2.1 | CC: | bperkins, chrisw, dallan, jkt, jruzicka, mlopes, ndipanov, oblaut, pbrady, sclewis | |
Target Milestone: | Upstream M2 | |||
Target Release: | 4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-quantumclient-2.2.1-2.el6ost | Doc Type: | Bug Fix | |
Doc Text: |
Prior to this update, older versions of python-cliff were incompatible with Python 2.6. Consequently, python-quantumclient with Python 2.6 and older python-cliff produced errors.
This fix addresses the issue by requiring python-cliff version 1.3 or higher, which provides Python 2.6 compatibility.
As a result, python-quantumclient can be used with Python 2.6.
|
Story Points: | --- | |
Clone Of: | ||||
: | 980964 (view as bug list) | Environment: | ||
Last Closed: | 2013-10-29 17:57:34 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 980964 |
Description
Brent Eagles
2013-06-07 18:55:33 UTC
Please note that this bug is only for updating the dependency info in the python-quantumclient spec file to specify python-cliff version 1.3 or newer. I've tried to verified it on Havana running rhel6.5 with: python-neutronclient-2.2.6-1.el6ost.noarch Though the python-cliff version is: python-cliff-1.4.4-1.el6ost.noarch Which is later then 1.3, but looking at the dependencies of of the neutronclient I saw that it only requiers: python-cliff >= 1.0 Which might cause problems if it needs 1.3 or later. As I wrote earlier it looks like some repos has been updated which might cause the proper version to be installed (python-cliff-1.4.4-1.el6ost.noarch), but without them, due to current dependency you might find yourself with older version (such as 1.0). We are providing distribution as a whole. If we require feature from python-cliff 1.3, we can just backport the feature to 1.0 (as an example) and in that case there is no reason to require 1.3. No one cares about really checking minimal required version upstream. These are just few reasons why we don't depend on versions if at all possible and instead just provide the right packages. IMHO this bug should be closed as soon as python-cliff 1.3 is available What do you say, Pádraig, should I explicitly require python-cliff >= 1.3 here? For some reason >= 1.0 is required already. We should avoid explicit version deps. The only caveat is where we need to force an update within a RHOS release. (updates between releases will/should involve a yum update, which will apply the required update automatically without needing the version dep). Given RHOS 3.0 and RHOS 4.0 have cliff 1.3 in the repos already, I'm closing this. |