Skip to content

config_reload() options for CACL cleanup_scale_rules() function#22718

Open
madbabu-cisco wants to merge 1 commit intosonic-net:masterfrom
madbabu-cisco:test-cacl-scale-rules-ipv6-memory-increase-threshold
Open

config_reload() options for CACL cleanup_scale_rules() function#22718
madbabu-cisco wants to merge 1 commit intosonic-net:masterfrom
madbabu-cisco:test-cacl-scale-rules-ipv6-memory-increase-threshold

Conversation

@madbabu-cisco
Copy link

@madbabu-cisco madbabu-cisco commented Mar 4, 2026

Description of PR

Config reload options for CACL cleanup_scale_rules() function

Summary:
Fixes # (issue)

For a long time, it is observed that the test_cacl_scale_rules_ipv6 test case fails due to Increase in Memory threshold. And it also, reported an incorrect percentage in increase in System Memory.

Debugging the issue, it was found that cleanup_scale_rules() which was called as part of previous test case test_cacl_scale_rules_ipv4() teardown function, actually invokes config_reload() which does not complete the restart of syncd process fully. Hence, the VM RSS memory occupied by syncd is too low, which eventually becomes normal. So, the difference between "Before test" and "After test" "free -m" command "used" field increases more than 20% causing the test case to fail. Fixed it with adding to the config_reload() option of wait_for_bgp = True, which fixes the issue.

There was also a cosmetic issue of reporting Increased MB usage as Increased percentage usage. Fixed this issue also.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

This CICD defect is there nearly for more than 3 months and the defect was frequently reproducible.

How did you do it?

Made the above two code changes required for threshold output formatting and fixed cleanup issue causing false positive

How did you verify/test it?

Added the fix and rerun the test

Any platform specific information?

It is across platforms - t0, t1 and t2.

Supported testbed topology if it's a new test case?

Existing test case

Documentation

Signed-off-by: Madhan Babu <madbabu@cisco.com>
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Mar 4, 2026

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: madbabu-cisco / name: Madhan Babu (bc28ee7)

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants