Bug 1872593 - [Rados]: monitor crashes and upgrade from 3.3z6 to 4.1z1 fails on bare-metal(rpm)
Summary: [Rados]: monitor crashes and upgrade from 3.3z6 to 4.1z1 fails on bare-metal(...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z7
: 3.3
Assignee: Neha Ojha
QA Contact: Manohar Murthy
Aron Gunn
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2020-08-26 07:20 UTC by Ameena Suhani S H
Modified: 2020-11-08 18:24 UTC (History)
17 users (show)

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.
Clone Of:
Environment:
Last Closed: 2020-11-08 18:24:16 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 47153 0 None None None 2020-08-28 21:17:20 UTC

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?
Note You need to log in before you can comment on or make changes to this bug.