Fix #54321
openosd/OSDMap: OSDMap CRC inconsistence with incremental
0%
Description
Operation of CEPH in a mixed cluster consisting of little and big endian nodes triggers CRC inconsistency during OSDMap incremental update in
OSD::handle_osd_map().
Initial check revealed that the OSDMap::crc is not equal to the OSDMap::Incremental::full_crc
and the OSDMap::crc is not properly calculated in the "void OSDMap::encode(ceph::buffer::list& bl, uint64_t features) const" function.
A typical warning message "failed to encode map" is logged (see the screensot in the attach).
Files
Updated by Laura Flores about 2 years ago
Hello, I don't see a screenshot. Can you try re-attaching it?
Updated by Laura Flores about 2 years ago
- Status changed from New to Fix Under Review
Updated by Aliaksei Makarau about 2 years ago
- File failed_to_encode.png failed_to_encode.png added
Dear Laura,please find the screenshot.
This issue we found originally for octopus (please see the issue 54320) and this fix is relevant to the master too.
Updated by Aliaksei Makarau about 2 years ago
Dear Laura,
this fix (originally found) is related to the octopus release:
https://tracker.ceph.com/issues/54320
the commit is here:
https://github.com/ibm-s390-cloud/ceph/commit/89153177a360d6b2f0bf91ba3df5c0f527c02ae2
Thank you!
Updated by Laura Flores about 2 years ago
- Is duplicate of Bug #54320: osd/OSDMap: OSDMap CRC inconsistence with incremental added