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 1636243

Summary: mon/HealthMonitor: do not send MMonHealthChecks to pre-luminous mon
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Neha Ojha <nojha>
Component: RADOSAssignee: Neha Ojha <nojha>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: high Docs Contact:
Priority: high    
Version: 3.1CC: ceph-eng-bugs, ceph-qe-bugs, dzafman, kchai, nojha, pbyregow, rperiyas, tchandra
Target Milestone: z1   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.5-55.el7cp Ubuntu: ceph_12.2.5-40redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-09 01:00:57 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:

Description Neha Ojha 2018-10-04 19:55:10 UTC
Description of problem:

During upgrade, we start doing the new health check code, but if we are
not the leader we can't send the new MMonHealthChecks message to the leader
or else it will crash.

Comment 7 Neha Ojha 2018-10-08 20:47:56 UTC
Steps to verify this bz:

1. Upgrade from jewel to luminous, make sure client workloads are running during the upgrade

2. Ensure than the MONs come up fine and there are no messages like
"can't decode unknown message type 1544 MSG_AUTH=17" in the logs

Comment 11 errata-xmlrpc 2018-11-09 01:00:57 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-2018:3530