4c736f177851cbf9fb7a6790282306ffac5065f8 (the current git submodule hash for octopus) is in origin/ceph-octopus-v5.8-1435. ac304adf46ff073a943d1ab2f6de0623c8ad6d86 (the RelWithDebInfo patch) is in origin/ceph-pacific-v6.8.1-1. So it seems we'll pick this fix up naturally when the ceph pacific package is uploaded, but pacific isn't due to release until March 2021.
Ideally we would pick this up from upstream rather than cherry-picking to the package. I'm not sure what the process is for cherry-picking patches to the ceph-octopus-v5.8-1435 rocksdb branch is upstream. The last update is from Apr 2019 so obviously it remains quite stable. I imagine they have a process for accepting cherry-picks into stable branches but we'd have to see if this would qualify.
@Ponnuvel, Thanks for the details.
4c736f177851cbf 9fb7a6790282306 ffac5065f8 (the current git submodule hash for octopus) is in origin/ ceph-octopus- v5.8-1435. ac304adf46ff073 a943d1ab2f6de06 23c8ad6d86 (the RelWithDebInfo patch) is in origin/ ceph-pacific- v6.8.1- 1. So it seems we'll pick this fix up naturally when the ceph pacific package is uploaded, but pacific isn't due to release until March 2021.
Ideally we would pick this up from upstream rather than cherry-picking to the package. I'm not sure what the process is for cherry-picking patches to the ceph-octopus- v5.8-1435 rocksdb branch is upstream. The last update is from Apr 2019 so obviously it remains quite stable. I imagine they have a process for accepting cherry-picks into stable branches but we'd have to see if this would qualify.