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 1633748

Summary: switch from civetweb to beast when upgrading from 3.1 to 3.2
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasu Kulkarni <vakulkar>
Component: Ceph-AnsibleAssignee: Dimitri Savineau <dsavinea>
Status: CLOSED ERRATA QA Contact: Uday kurundwade <ukurundw>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2CC: aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, dwojewod, gmeno, jharriga, nthomas, tchandra, tserlin
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.0-0.1.rc4.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:44: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:
Bug Depends On:    
Bug Blocks: 1641792, 1750994    

Description Vasu Kulkarni 2018-09-27 16:00:50 UTC 
Description of problem:

Doug brought up this point in IRC, when we are doing upgrade from 2.x/3.1 to 3.2 instead of admin manually switch from civetweb to beast, ceph-ansible should take care of that to avoid any user error.
Comment 3 Vasu Kulkarni 2018-09-27 17:26:32 UTC 
Harish pointed out this is a tech preview, so moving the target for 3.3
Comment 5 Giridhar Ramaraju 2019-08-05 13:12:02 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 6 Giridhar Ramaraju 2019-08-05 13:12:53 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 16 errata-xmlrpc 2020-01-31 12:44:52 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:0312