Bug 1793079 - [RFE] Removal of Paunch
Summary: [RFE] Removal of Paunch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 17.0 (Wallaby)
Hardware: All
OS: All
high
low
Target Milestone: Alpha
: 17.0
Assignee: Lon Hohberger
QA Contact: Jon Schlueter
URL:
Whiteboard:
Depends On:
Blocks: 1811079
TreeView+ depends on / blocked
 
Reported: 2020-01-20 16:03 UTC by Emilien Macchi
Modified: 2022-09-21 12:10 UTC (History)
10 users (show)

Fixed In Version: tripleo-ansible-0.4.2-0.20200226055425.888f6d7.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-21 12:09:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3059 0 None None None 2022-02-05 09:16:17 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:10:59 UTC

Description Emilien Macchi 2020-01-20 16:03:37 UTC
Description of problem:
This RFE is part of the Simplifications efforts in TripleO which aim to reduce the number of tools used by our deployment framework.

Paunch can be replaced by a new ansible role:
https://docs.openstack.org/tripleo-ansible/latest/roles/role-tripleo-container-manage.html

This BZ is used for tracking the backport of this feature into OSP16 zstream.

Comment 6 Cédric Jeanneret 2020-08-20 07:28:07 UTC
Hello Emilien,

Care to raise a BZ against "distribution" component in order to drop paunch packages from the release?

Thank you!

C.

Comment 15 errata-xmlrpc 2022-09-21 12:09:13 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543


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