Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1511954

Summary: Move puppet-tempest to dev channel with packstack
Product: Red Hat OpenStack Reporter: Chandan Kumar <chkumar>
Component: puppet-tempestAssignee: Chandan Kumar <chkumar>
Status: CLOSED ERRATA QA Contact: Martin Kopec <mkopec>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: jjoyce, jschluet, matyoung, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: puppet-tempest-12.5.0-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:39:00 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:

Description Chandan Kumar 2017-11-10 13:50:24 UTC
puppet-tempest is consumed by packstack for configuring tempest and packstack is not supported by Red Hat. It would be good to move puppet-tempest to a seperate channel.

Comment 1 Matt Young 2018-04-16 16:24:20 UTC
- Upstream patches have merged.

Comment 6 Martin Kopec 2018-05-02 11:19:48 UTC
The puppet-tempest package is since 2018-04-19.2 puddle not more available in RH7-RHOS-13.0 channel.

puppet-tempest package was moved to RH7-RHOS-DEVTOOLS-13.0 channel and the newest version of puppet-tempest-12.5.0-1.el7ost is available there since 2018-04-19.2 puddle.

Marking bug as verified.

Comment 8 errata-xmlrpc 2018-06-27 13:39:00 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.