Bug 1834334 - Drop puppet-tempest from RHOS-16.1
Summary: Drop puppet-tempest from RHOS-16.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 16.1 (Train on RHEL 8.2)
Assignee: shreshtha joshi
QA Contact: Jon Schlueter
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-11 14:18 UTC by Chandan Kumar
Modified: 2020-07-29 07:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1834328
Environment:
Last Closed: 2020-07-29 07:52:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3148 0 None None None 2020-07-29 07:52:57 UTC

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


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