Bug 1691283

Summary:	need to add a step to finalize process of upgrading Ceph
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Servesha <sdudhgao>
Component:	Documentation	Assignee:	John Brier <jbrier>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ameena Suhani S H <amsyedha>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	agunn, amsyedha, asriram, hyelloji, jbrier, kdreyer, kjosy
Target Milestone:	rc
Target Release:	4.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHCS 4.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-04 10:26:50 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:	1687793, 1809603

Description Servesha 2019-03-21 10:45:26 UTC

Description of problem: In upgrading RHCS documentation, it needs to be explicitly mention to finalize the process as last step - "a VM restart or live-migration is *necessary* to get the new ceph-version running and it is not enough to only update the ceph-packages"


Version-Release number of selected component (if applicable): After upgrading from one version to other version.


How reproducible: 


Steps to Reproduce:
1.
2.
3.

Actual results: 


Expected results:


Additional info: To finalize the upgrading steps, it is needful to mention as a last step that - "a client VMs a VM restart or live-migration is necessary to get the new ceph-version running and it is not enough to only update the ceph-packages".

The reason is - For the VM/qemu to use the newer librbd/ceph that were just upgraded,a live-migration or rebooting VMs is necessary.

The upgrading doc needs changes such as : 

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/installation_guide_for_ubuntu/upgrading_ceph_storage_cluster

Comment 1 Giridhar Ramaraju 2019-08-05 13:08:38 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 2 Giridhar Ramaraju 2019-08-05 13:10:03 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 4 John Brier 2020-02-21 20:58:53 UTC

That doc is for RHCS 2 which is no longer supported. That said, I see the problem in "Upgrading a Ceph Client Node", [1] if you're using the ceph-client with qemu-kvm you need to restart the vm or do a live migration. 

In the RHCS 3 docs (which are still supported) we do cover this issue, in fact there is a note that the VMs must be stopped and started, not just restarted. [2]

In the RHCS 4 docs (latest supported version) we don't have a section on upgrading ceph client nodes. We just have a general upgrading chapter. [3] It does mention that the ansible playbooks update the client nodes last. I will add a final step that says to restart any applications using the ceph client, like the one that is in the RHCS 3 docs [2].

1) https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/installation_guide_for_ubuntu/upgrading_ceph_storage_cluster#upgrading_a_ceph_client_node
2) https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/installation_guide_for_red_hat_enterprise_linux/index#upgrading-a-ceph-client-node
3) https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/installation_guide/index#upgrading-a-red-hat-ceph-storage-cluster