Bug 1431760 - Packaging Tempest to be included in RHOSP12
Summary: Packaging Tempest to be included in RHOSP12
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Upstream M2
: 12.0 (Pike)
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-13 17:14 UTC by Maria Bracho
Modified: 2018-02-05 19:04 UTC (History)
6 users (show)

Fixed In Version: openstack-tempest-16.0.1-0.20170710180247.de46ed8.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:15:40 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Maria Bracho 2017-03-13 17:14:10 UTC 
Description of problem:
Need a package to distribute Tempest in RHOSP12.
Comment 1 Red Hat Bugzilla Rules Engine 2017-03-13 17:15:10 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 2 Red Hat Bugzilla Rules Engine 2017-03-15 00:52:45 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 3 Red Hat Bugzilla Rules Engine 2017-03-15 10:48:33 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 4 Martin Magr 2017-07-18 09:18:22 UTC 
The Tempest package is pulled from RDO to downstream automatically.
Comment 6 Martin Kopec 2017-10-25 11:23:38 UTC 
Tempest was packaged to a openstack-tempest-16.0.1-0.20170710180247.de46ed8.el7ost package for tempest distribution in ROSP12. Therefor I'm marking this bug as verified.
Comment 9 errata-xmlrpc 2017-12-13 21:15:40 UTC 
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-2017:3462
Note You need to log in before you can comment on or make changes to this bug.