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 1541010

Summary: Update the container upgrade article for 2.5 to include rolling update from 2.4 to 2.5
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: DocumentationAssignee: Erin Donnelly <edonnell>
Status: CLOSED CURRENTRELEASE QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.5CC: asriram, edonnell, hnallurv, jquinn, kdreyer
Target Milestone: rc   
Target Release: 2.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-26 06:55:46 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: 1532294    

Description Vasishta 2018-02-01 14:13:28 UTC
Description of problem:
As rolling_update of containerized cluster from 2.4 to 2.5 is supported, We need 
to add steps in article "Updating Red Hat Ceph Storage deployed as a Container Image" to guide users to upgrade containerized cluster from 2.4 to 2.5 using ceph-ansible.

Steps -

1) Enable the Red Hat Ceph Storage 2 Tools repository:

Command - # subscription-manager repos --enable=rhel-7-server-rhceph-2-tools-rpms

2) Update ceph-ansible

Command - #yum update ceph-ansible

3) Navigate to the /usr/share/ceph-ansible/ directory: 

Command - $ cd /usr/share/ceph-ansible/

4) In the group_vars/all.yml file change the ceph_docker_image_tag parameter to point to the newer Ceph container version, for example: 

ceph_docker_image_tag: 2.5

5)  If the cluster you want to upgrade contains any Ceph Object Gateway nodes, add the radosgw_interface parameter to the group_vars/all.yml file.

radosgw_interface: <interface>

6) Copy rolling_update.yml from the infrastructure-playbooks directory to the current directory.

# cp infrastructure-playbooks/rolling_update.yml .

7)  Run the playbook:
$ ansible-playbook rolling_update.yml -e  jewel_minor_update=true


---------------------------------------------

QE is not sure about whether to retain steps guiding manual way of upgrading cluster as rolling update was not supported for previous releases.

Comment 6 Vasishta 2018-02-05 06:58:43 UTC
Looks good, Moving BZ to VERIFIED state

Regards,
Vasishta

Comment 9 Red Hat Bugzilla 2023-09-15 00:06:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days