mirror of
https://github.com/ceph/ceph
synced 2025-01-22 19:15:41 +00:00
328271d587
With mclock scheduler enabled, the recovery throughput is throttled based on factors like the type of mclock profile enabled, the OSD capacity among others. Due to this the recovery times may vary and therefore the existing timeout of 120 secs may not be sufficient. To address the above, a new method called _is_inprogress_or_complete() is introduced in the TestProgress Class that checks if the event with the specified 'id' is in progress by checking the 'progress' key of the progress command response. This method also handles the corner case where the event completes just before it's called. The existing wait_until_true() method in the CephTestCase Class is modified to accept another function argument called "check_fn". This is set to the _is_inprogress_or_complete() function described earlier in the "test_turn_off_module" test that has been observed to fail due to the reasons already described above. A retry mechanism of a maximum of 5 attempts is introduced after the first timeout is hit. This means that the wait can extend up to a maximum of 600 secs (120 secs * 5) as long as there is recovery progress reported by the 'ceph progress' command result. Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com> |
||
|---|---|---|
| .. | ||
| dashboard | ||
| __init__.py | ||
| mgr_test_case.py | ||
| test_crash.py | ||
| test_dashboard.py | ||
| test_failover.py | ||
| test_insights.py | ||
| test_module_selftest.py | ||
| test_orchestrator_cli.py | ||
| test_progress.py | ||
| test_prometheus.py | ||