Skip to content

Conversation

@SrinivasaBharath
Copy link
Contributor

Description

The Fix includes the -

  1. Automation to verify the osd_scrub_load_threshold with high CPU load using stress-ng.
    a. Install stress-ng package on all rados nodes
    b. Start stress-ng to continuously generate load
    c. Monitoring load continuously to verify it increases and calculate load threshold.The formula used to calculate the load is-
    Load_threshold = load_avgerage / online_cpu_count
    Where
    Load average is clculated by executing the "/proc/loadavg" command
    online_cpu_count is found by executing the nproc command
    d. Wait for load threshold (loadavg / online CPUs) to exceed 15
    e. Set the osd_scrub_load_threshold to 10(Default)
    f. Set the debug_osd and debug_mon to 20
    g. Start the user initiated scrub and check that the scrub should not get start if the load is high
    h. Check logs for scrub_load_below_threshold messages

  2. Divided the scenarios in to separate tests

  3. Uncommented the Verification of the osd_scrub_load_threshold parameter with the default value which is 10.0

Abandoning the following PR due to history issues and I re-open this new PR.All the review commnets can see at the below PR.
PR - #5549

Please include Automation development guidelines. Source of Test case - New Feature/Regression Test/Close loop of customer BZs

click to expand checklist
  • Create a test case in Polarion reviewed and approved.
  • Create a design/automation approach doc. Optional for tests with similar tests already automated.
  • Review the automation design
  • Implement the test script and perform test runs
  • Submit PR for code review and approve
  • Update Polarion Test with Automation script details and update automation fields
  • If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: SrinivasaBharath
Once this PR has been reviewed and has the lgtm label, please assign neha-gangadhar for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added RADOS Rados Core ceph-ci-review waiting review from cephci do-not-merge/hold Do not merge labels Jan 13, 2026
@SrinivasaBharath SrinivasaBharath removed the do-not-merge/hold Do not merge label Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ceph-ci-review waiting review from cephci RADOS Rados Core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant