Bug 1007994
| Summary: | neutron requires pyparsing 1.5.7 but we only provide it up to 1.5.6 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Giulio Fidente <gfidente> |
| Component: | python-quantumclient | Assignee: | Terry Wilson <twilson> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ofer Blaut <oblaut> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.0 | CC: | chrisw, gfidente, hateya, jruzicka, mkollaro, pbrady, yeylon |
| Target Milestone: | async | Keywords: | ZStream |
| Target Release: | 3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-05 04:03:22 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: | |||
Terry / Padraig - is this a bogus requirement, or is there some functional difference that we need to deal with here? I tried to reproduce this on 2013.1.3 and 2013.1.4 builds, and did not have any issue: [root@localhost ~(keystone_admin)]# /usr/bin/quantum net-list --format=csv "id","name","subnets" "771d9e2d-96be-40b3-9788-5ca21f95b294","private","7ef8f900-2c0f-4638-9c7a-d11afd56b3b3 10.0.0.0/24" "f7841a53-a74e-42b9-8a2e-50623a284eea","public","c6d2d282-3e25-4295-a5c5-bb54c17cb57e 172.24.4.224/28" [root@localhost ~(keystone_admin)]# rpm -q pyparsing openstack-quantum pyparsing-1.5.6-1.el6.noarch openstack-quantum-2013.1.4-2.el6ost.noarch So 1.5.6 -> 1.5.7 was made in grizzly indirectly due to python 3 adjustments http://pad.lv/1191866 which leads to... http://trac-hg.assembla.com/python-cmd2/rev/a5f3d5a89d6c That commit again only references python 3 stuff, and not whether python-cmd2 actually does need >= 1.5.7 I suspect that was the latest 1.5.x release at the time of the commit which I've seen people reference for some unknown reason So 2 issues. 1. 1.5.7 is probably a false requirement. 1.5.6 is fine. 2. There should be no runtime dep management in released packages. I thought the quantumclient package might be referencing it, but version 2.2.1 seems to avoid the runtime check, which seems to be for version 1.5.6 in any case. Could you please search for which egg has pyparsing==1.5.7 present. Thanks, I just went through a packstack --allinone with the 2013-11-01.1 puddle and did not get this error. This appears to be a false requirement *and* to no longer be an issue. Giulio Fidente: Can you verify that this issue no longer occurs so we can close the issue? Confirmed, not an issue with 2013-11-01.1 anymore. I also don't seem to find any reference to pyparsing 1.5.7 in pip-requires from stable/grizzly at all in github https://github.com/openstack/requirements/blob/stable/grizzly/tools/pip-requires For future reference, the actual quantum/neutron client packaged with the build 2013-09-06.2 is python-quantumclient-2.2.1-2.el6ost.noarch.rpm Closing as it seems to have, at the very least, been fixed already. |
Description of problem: packstack installation fails with the followin ERROR : Error during puppet run : err: Could not prefetch quantum_network provider 'quantum': Execution of '/usr/bin/quantum net-list --format=csv --column=id --quote=none' returned 1: (pyparsing 1.5.6 (/usr/lib/python2.6/site-packages), Requirement.parse('pyparsing==1.5.7')) apparently neutron requires pyparsing 1.5.7, we only provide it in version 1.5.6 Version-Release number of selected component (if applicable): openstack-quantum-2013.1.3-1.el6ost.noarch How reproducible: try to install using packstack