Bug 1348609
Summary: | python-colorama should be a dependency of python-gabbi | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Anshul Behl <abehl> |
Component: | python-colorama | Assignee: | Jason Joyce <jjoyce> |
Status: | CLOSED ERRATA | QA Contact: | Arik Chernetsky <achernet> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.0 (Mitaka) | CC: | apevec, jjoyce, jschluet, lhh, markmc, mburns, mlammon, mlopes, slinaber, srevivo, tvignaud |
Target Milestone: | ga | ||
Target Release: | 9.0 (Mitaka) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-colorama-0.3.7-2.el7ost | Doc Type: | Enhancement |
Doc Text: |
The python-colorama package has been added to Red Hat OpenStack Platform 9.
This package is an install dependency for python-gabbi, which in turn is required by openstack-gnocchi.
As a result, openstack-gnocchi and python-gabbi install without dependency errors.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-11 12:27:24 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: |
Description
Anshul Behl
2016-06-21 14:54:23 UTC
I have OSP 9.0 installed from 02 AUG 16 I see these files are present in repo [stack@instack rhos-qe-core-installer]$ repoquery --requires --recursive --resolve python-gabbi | grep python-colorama python-colorama-0:0.3.7-2.el7ost.noarch [stack@instack rhos-qe-core-installer]$ rpm -qa python-gabbi python-gabbi-1.22.0-1.el7ost.noarch [stack@instack rhos-qe-core-installer]$ rpm -qa python-colorama python-colorama-0.3.7-2.el7ost.noarch In addition, checked latest repo and files are present http://download.eng.bos.redhat.com/rcm-guest/puddles/OpenStack/9.0-RHEL-7/2016-08-04.1/RH7-RHOS-9.0/x86_64/os/Packages/ 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://rhn.redhat.com/errata/RHEA-2016-1597.html |