Bug 1441228 - Rebase openstack-tempest to tag 16.0.0
Summary: Rebase openstack-tempest to tag 16.0.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z1
: 11.0 (Ocata)
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
: 1461192 1467820 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 13:07 UTC by Chandan Kumar
Modified: 2020-09-10 10:27 UTC (History)
11 users (show)

Fixed In Version: openstack-tempest-16.0.0-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-19 17:11:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 456837 0 None MERGED Release Tempest 16.0.0 2020-08-30 10:02:07 UTC
RDO 6295 0 None None None 2017-04-26 08:41:09 UTC
RDO 6296 0 None None None 2017-04-26 08:40:19 UTC
RDO 6375 0 None None None 2017-04-26 08:41:34 UTC
Red Hat Product Errata RHBA-2017:1786 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory 2017-07-19 21:10:33 UTC

Description Chandan Kumar 2017-04-11 13:07:40 UTC
The upstream OpenStack tempest tag 16.0.0 marks the end of support for Mitaka in Tempest. It will support Newton and Ocata release. Current RHOS-11 tempest rpm contains the tempest-15.0.0 tag. We need to rebase tempest rpm to tag 16.0.0

Comment 2 Fabio Massimo Di Nitto 2017-06-19 14:54:21 UTC
*** Bug 1461192 has been marked as a duplicate of this bug. ***

Comment 4 Martin Kopec 2017-07-03 12:31:09 UTC
The package was rebased to tag 16 and it's already available for Red Hat Openstack as openstack-tempest-16.0.0-1.el7ost

Comment 5 Prateek Arora 2017-07-05 09:54:32 UTC
*** Bug 1467820 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2017-07-19 17:11:41 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/RHBA-2017:1786


Note You need to log in before you can comment on or make changes to this bug.