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 1828069

Summary: [Docs][Ceph] Upgrade section does not mention about converting civetweb to beast
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mustafa Aydın <maydin>
Component: DocumentationAssignee: John Brier <jbrier>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: asriram, jbrier, kdreyer
Target Milestone: z2   
Target Release: 4.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-03 19:56:17 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:
Bug Depends On:    
Bug Blocks: 1859104    

Description Mustafa Aydın 2020-04-26 15:54:25 UTC
Description of problem:
If the Customer was using the Civetweb at RHCS3 (which is the default frontend), the RGWs will switch to Beast as mentioned at [1]. I recommend to add a warning to the upgrade section [2] about it as the Customer may need to change some configurations at their infra or ceph cluster accordingly [3].

[1]https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/object_gateway_configuration_and_administration_guide/index#using-the-beast-front-end-rgw

[2]https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/installation_guide/index#upgrading-a-red-hat-ceph-storage-cluster

[3] https://bugzilla.redhat.com/show_bug.cgi?id=1828060

Version-Release number of selected component (if applicable):
RHCS 4.x

Comment 1 John Brier 2020-04-28 15:19:00 UTC
Thanks for opening bugs on Civetweb/Beast info in the docs, Mustafa.

Sorry for the incorrect/inconsistent info.

We will get it updated correctly.