Bug #23130
openNo error is shown when "osd_mon_report_interval_min" value is greater than "osd_mon_report_interval_max" value.
0%
Description
Execution Steps:
------------------
1. Set the "osd_mon_report_interval_min" value using CLI
# ceph daemon osd.1 config set osd_mon_report_interval_min 20
2. Set the "osd_mon_report_interval_max" value to 4 using CLI
# ceph daemon osd.1 config set osd_mon_report_interval_max 4
Observation:
-------------
As per ceph guideline the value of "osd_mon_report_interval_max" must be greater than or equal to "osd_mon_report_interval_min" value to work ceph osd properly.
But there is no error message shown when the user trying to set the wrong combination.
We have set below values for osd0, osd1 and osd2:
osd_mon_report_interval_min = 20
osd_mon_report_interval_max = 12
Whenever (osd_mon_report_interval_min > osd_mon_report_interval_max), it considers value for "osd_mon_report_interval_max" as minimum interval value.
Here mon osd report interval ( event::pg_stats) is set to 12 and behaves accordingly.
Solution:
-----------
There should be a data validation between "osd_mon_report_interval_max" and "osd_mon_report_interval_min" value when the user try to set these values using CLI.
Files