Bug 1622011
| Summary: | Rebase python-tempestconf to 2.0.0 for RHOS-14 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Martin Kopec <mkopec> |
| Component: | python-tempestconf | Assignee: | Chandan Kumar <chkumar> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Kopec <mkopec> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 14.0 (Rocky) | CC: | chkumar, jamsmith, udesale |
| Target Milestone: | beta | Keywords: | Rebase, Triaged, ZStream |
| Target Release: | 14.0 (Rocky) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
Rebase package(s) to version:
python-tempestconf-2.0.0
In this rebase, the python-tempestconf tool went through a major refactoring to ease the process of generating tempest.conf.
This rebase also fixes many outstanding bugs and brings support for new services.
Moving to the new release provides many benefits to tempest users.
For details, see the OpenStack release notes:
https://docs.openstack.org/releasenotes/python-tempestconf/unreleased.html#relnotes-2-0-0
|
Story Points: | --- |
| Clone Of: | 1621205 | Environment: | |
| Last Closed: | 2019-01-11 11:51:27 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: | 1507412, 1557736, 1564866, 1569613, 1599372 | ||
|
Description
Martin Kopec
2018-08-24 07:21:44 UTC
The python-tempestconf-2.0.0 package is available since 2018-09-05.1 puddle. Rebase completed, marking as VERIFIED. 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 |