Bug 1834334

Summary:	Drop puppet-tempest from RHOS-16.1
Product:	Red Hat OpenStack	Reporter:	Chandan Kumar <chkumar>
Component:	distribution	Assignee:	shreshtha joshi <shrjoshi>
Status:	CLOSED ERRATA	QA Contact:	Jon Schlueter <jschluet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	jjoyce, jschluet, lhh, mburns, shrjoshi
Target Milestone:	beta	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1834328	Environment:
Last Closed:	2020-07-29 07:52:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chandan Kumar 2020-05-11 14:18:31 UTC

+++ This bug was initially created as a clone of Bug #1834328 +++

puppet-tempest was used with packstack to run and configure tempest tests. We no longer use puppet-tempest for running tempests and not maintained.

Tempest tests are runned by the developer manually using openstack-tempest. It contains all the batteries included for that.

Since puppet-tempest is no longer used. So I think we can drop it from release.

Comment 1 Jon Schlueter 2020-05-11 14:22:21 UTC

need to make sure it is not referenced or installed in container images or included in composes directly or indirectly.

<chandankumar> jschlueter, it is shipped as a part of tripleo-puppet-elements https://review.rdoproject.org/r/gitweb?p=openstack/tripleo-puppet-elements.git;a=blob;f=elements/puppet-modules/environment.d/02-puppet-modules-install-types.sh#l53

Comment 7 errata-xmlrpc 2020-07-29 07:52:44 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-2020:3148