Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2094241

Summary:	[cee/sd][Doc] Need to modify the bucket lifecycle chapter name in the object storage administration guide in RHCS 4.x
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Kritik Sachdeva <ksachdev>
Component:	Documentation	Assignee:	ceph-docs <ceph-docs>
Documentation sub component:	Object Gateway Guide	QA Contact:	Madhavi Kasturi <mkasturi>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	ekristov, hklein, sourdas
Version:	4.2
Target Milestone:	---
Target Release:	6.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-07 11:22:52 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 Kritik Sachdeva 2022-06-07 09:27:05 UTC

Describe the issue:
In the object storage administration guide for chapter-10 of bucket lifecycle, it is mentioned in the chapter heading as this is a Technology preview feature. But in the next para for Important note it is mentioned that the only bucket transition rule is a Technology preview feature.

It is creating a confusion as if the complete bucket lifecycle or only the transition rule is a TP feature. 

So, can you please confirm the same and then modify the doc as needed?

Document URL: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/object_gateway_configuration_and_administration_guide/index#bucket-lifecycle

Chapter/Section Number and Title: 3.10. Bucket lifecycle (Technology Preview)

Product Version: RHCS 4.x

Comment 4 Eliska 2022-07-07 11:22:52 UTC


*** This bug has been marked as a duplicate of bug 2094283 ***

Comment 5 Eliska 2022-07-07 11:23:41 UTC

The update will be published in the upcoming weekly async