Bug 1819829 - Packstack removal
Summary: Packstack removal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 16.1 (Train on RHEL 8.2)
Assignee: Lon Hohberger
QA Contact: Jon Schlueter
URL:
Whiteboard:
Depends On: 1819830
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-01 16:39 UTC by Alan Pevec
Modified: 2020-07-29 07:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1819830 (view as bug list)
Environment:
Last Closed: 2020-07-29 07:51:07 UTC
Target Upstream Version:
Embargoed:
scohen: needinfo+


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:51:27 UTC

Description Alan Pevec 2020-04-01 16:39:22 UTC
As documented in https://access.redhat.com/articles/2477851
Packstack is not supported installer for OSP and has been delivered in separate devtools channel since OSP 10.

In https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/product_guide/index#sect-installation-summary
it was documented with a NOTE: Packstack deployments are intended only for POC-type testing environments and are not suitable for production.

Since OSP 16, there is supported TripleO/Director standalone for this type of PoC installations:
https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/standalone.html

To avoid confusion, please remove openstack-packstack in OSP16.1

NB KB https://access.redhat.com/articles/1127153 will also need to be update to point to the TripleO/Director standalone.

Comment 9 errata-xmlrpc 2020-07-29 07:51:07 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.