Bug 1544804 – Retire python-tempest-lib from RHOS-13

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1544804 - Retire python-tempest-lib from RHOS-13

Summary:	Retire python-tempest-lib from RHOS-13

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	python-tempest-lib (Show other bugs)
Sub Component:
Version:	13.0 (Queens)
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	beta
Target Release:	13.0 (Queens)
Assigned To:	Jon Schlueter
QA Contact:	Martin Kopec
Docs Contact:

URL:
Whiteboard:
Keywords:	TestOnly, Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-02-13 09:36 EST by Chandan Kumar
Modified:	2018-07-09 07:23 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Deprecated Functionality
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-06-27 09:44:34 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
RDO	12123	None	None	None	2018-02-13 09:36 EST
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:45 EDT

Groups: None (edit)

Description Chandan Kumar 2018-02-13 09:36:44 EST

tempest-lib is removed upstream long time back in favour of tempest.lib api.
Once an user upgrades the package to Queens, It can create conflicts. so it is better to obselete the package if already available on the environment.
Here is the review queue for the same in rdo: https://review.rdoproject.org/r/#/q/topic:obseletes_tempest_lib

Comment 2 Jon Schlueter 2018-02-15 10:03:04 EST

unused and now dropped from OSP 13

Comment 8 errata-xmlrpc 2018-06-27 09:44:34 EDT

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-2018:2086

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