Bug 1872593

Summary:	[Rados]: monitor crashes and upgrade from 3.3z6 to 4.1z1 fails on bare-metal(rpm)
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Ameena Suhani S H <amsyedha>
Component:	RADOS	Assignee:	Neha Ojha <nojha>
Status:	CLOSED WORKSFORME	QA Contact:	Manohar Murthy <mmurthy>
Severity:	high	Docs Contact:	Aron Gunn <agunn>
Priority:	unspecified
Version:	3.3	CC:	agunn, akupczyk, aschoen, bhubbard, ceph-eng-bugs, dzafman, giridhar.ramaraju, gmeno, jdurgin, kchai, nojha, nthomas, rzarzyns, sangadi, sostapov, sseshasa, ykaul
Target Milestone:	z7
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.Upgrading from {product} 3 to 4 can cause Ceph Monitors to crash Doing an upgrade from {product} 3 to 4 can cause newer Ceph Monitors to send an incompatible message to older Ceph Monitors. This can cause older Ceph Monitors to crash while trying to read the incompatible message. To work around this issue, start all Ceph Monitors running {product} 4. As a result, all Ceph Monitors will understand the new message.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-08 18:24:16 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:	1726135

Description Ameena Suhani S H 2020-08-26 07:20:16 UTC

Description of problem:
Monitor crashes and upgrade from 3.3z6 to 4.1z1 failed

Version-Release number of selected component (if applicable):
ceph-ansible-4.0.25.2-1.el7cp.noarch

How reproducible:
2/2

Steps to Reproduce:
1.Install 3.3z6(ceph-ansible-3.2.49-1.el7cp.noarch) cluster on bare-metal(rpm)
2. upgrade to 4.1z1(ceph-ansible-4.0.25.2-1.el7cp.noarch) from cdn


Actual results:
Upgrade fails and mon crash is seen

Expected results:
Upgrade should be successful

Comment 6 Josh Durgin 2020-08-26 15:21:17 UTC

To workaround this, upgrade the monitor and restart it.

The log shows all the restarts were still using luminous.

Comment 8 Scott Ostapovicz 2020-10-12 14:35:58 UTC

What is the status of this issue?  is it closed?