Bug 1623093
| Summary: | Gnocchi 4.3 append '+nnone' when built inside a container | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Filip Hubík <fhubik> | ||||
| Component: | gnocchi | Assignee: | Mehdi ABAAKOUK <mabaakou> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 14.0 (Rocky) | CC: | apevec, jjoyce, jschluet, lhh, mabaakou, mmagr, srevivo | ||||
| Target Milestone: | beta | Keywords: | Automation, AutomationBlocker, Triaged | ||||
| Target Release: | 14.0 (Rocky) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gnocchi-4.3.2-0.20180904144348.29b924e.el7ost | Doc Type: | No Doc Update | ||||
| Doc Text: |
-
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-01-11 11:51:31 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: | |||||||
| Attachments: |
|
||||||
|
Description
Filip Hubík
2018-08-28 13:04:31 UTC
It's break because the Gnocchi package version contains "+nnone" Need to figure out why. Version number looks wrong in spec file. %global dlrn_nvr gnocchi-4.3.1.dev2+nnone-0.20180808112157.711e51f %global dlrn 1 %define upstream_version 4.3.1.dev2+nnone I will look why dlrn generate this '+nnone' Looks like +nnone is generated by Gnocchi setup.py script but only in DLRN context. DLRN have two of hacks to remove this +..., we could add one more. Or better we can fix Gnocchi to never create the +XXXX part. I will do the second solution. Last RDO DLRN build is fixed: https://trunk.rdoproject.org/centos7-rocky/76/8f/768fc724f00eb63e84db1e9ec7f95aec226f2f9a_e82c2227/rpmbuild.log %global dlrn_nvr gnocchi-4.3.2.dev2-0.20180831100336.768fc72 %define upstream_version 4.3.2.dev2 Next RDO import will have the fixed spec I can not confirm this issue being fixed using gnocchi-4.3.2-0.20180831131143.768fc72.el7ost - I got several dependency errors running command (part of packstack deployment, puddle 2018-08-28.2):
$ gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf
1) Traceback (most recent call last):
File "/bin/gnocchi-upgrade", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3011, in <module>
parse_requirements(__requires__), Environment()
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 626, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: pyparsing>=2.2.0
With python2-pyparsing-2.2.0-3.el7ost.noarch.rpm I get:
2)
Traceback (most recent call last):
File "/bin/gnocchi-upgrade", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3011, in <module>
parse_requirements(__requires__), Environment()
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 626, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: setuptools>=30.3
$ rpm -qa | grep setuptools
python-setuptools-0.9.8-7.el7.noarch
Which is workaroundable with forced installation of pip and the newer setuptools into root system.
But with newer gnocchi packages from family of 4.3.2-0.20180904144348.29b924e packstack deployment passes without the issue described here,
with exception that python2-pyparsing-2.2.0-3.el7ost needs to be also pre-installed. Moving the fixed in version to gnocchi-4.3.2-0.20180904144348.29b924e then.
Newer puddle 2018-09-06.1 doesn't suffer from this issue and has never version included.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045 |