Bug 1700481

Summary:	Unclear if overcloud-secure and overcloud-secure-uefi are tech-preview in OSP 13
Product:	Red Hat OpenStack	Reporter:	Brian Smith <briasmit>
Component:	openstack-tripleo-image-elements	Assignee:	Bob Fournier <bfournie>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	aschultz, bfournie, jliberma, jslagle, mburns
Target Milestone:	z8	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-image-elements-8.0.2-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-03 16:55:32 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:
Embargoed:

Description Brian Smith 2019-04-16 17:05:29 UTC

Description of problem:
openstack-tripleo-image-elements-8.0.1-3.el7ost.noarch.rpm, /usr/share/tripleo-image-elements/overcloud-secure/README.rst and /usr/share/tripleo-image-elements/overcloud-secure-uefi/README.rst both state:

"CAUTION: This element is part of the security hardened images feature, that
is delivered in this release as tech preview. The following element is not
intended for production usage."

In the OSP 13 release notes, and in the Whole Disk Images documentation: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/appe-whole_disk_images it does not mention this being tech-preview.  

If it is tech-preview, can we get the documentation updated to reflect it being tech preview, and if it is not tech-preview in OSP 13 can we have these readme files within the RPM updated? 


Version-Release number of selected component (if applicable): openstack-tripleo-image-elements-8.0.1-3.el7ost.noarch.rpm

Comment 12 errata-xmlrpc 2019-09-03 16:55:32 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-2019:2624