Bug 1621205

Summary: Rebase python-tempestconf to 2.0.0 for RHOS-13
Product: Red Hat OpenStack Reporter: Chandan Kumar <chkumar>
Component: python-tempestconfAssignee: Chandan Kumar <chkumar>
Status: CLOSED ERRATA QA Contact: Martin Kopec <mkopec>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: knylande, udesale
Target Milestone: z3Keywords: Rebase, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tempestconf-2.0.0-1.el7ost Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase python-tempestconf to version 2 (package name python-tempestconf-2.0.0). The python-tempestconf tool went through a major refactoring to ease the process of generating tempest.conf. This version fixes many outstanding bugs and brings support for new services. Tempest users should benefit by moving to the new release.
Story Points: ---
Clone Of:
: 1622011 (view as bug list) Environment:
Last Closed: 2018-11-14 01:14:59 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:
Bug Depends On:    
Bug Blocks: 1599753    

Description Chandan Kumar 2018-08-23 14:16:22 UTC
python-tempestconf-2.0.0 is released recently.
The tool went through a major refactoring to ease the process of generating tempest.conf.
Here is the release notes: https://docs.openstack.org/releasenotes/python-tempestconf/unreleased.html#relnotes-2-0-0

It also fixes lots of outstanding bugs and bring support for new services for generating the same.
Moving to new release provides a lot of benefit to tempest users.

Here is the reviews link for RDO queens:
https://review.rdoproject.org/r/#/q/topic:tempestconf_queens

Comment 9 Martin Kopec 2018-10-25 07:50:22 UTC
The python-tempestconf-2.0.0 package is available since 2018-10-22.4 puddle. Rebase completed, marking as VERIFIED.

Comment 11 errata-xmlrpc 2018-11-14 01:14:59 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-2018:3611