[HA] [smartswitch] add ha steady traffic test with PL config

[aronovic]

Description of PR

HA test code with PL config and traffic

Summary:
Fixes # (issue)

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?

Add HA test with PL traffic

How did you do it?

Added tests

How did you verify/test it?

Run it on HA topology

Any platform specific information?

HA topology for MTFuji

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

HA topology

Documentation

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yxieca]

Blocking issues:

1. HA setup fixtures are empty: setup_dash_ha_from_json and activate_dash_ha_from_json in tests/ha/conftest.py are fixtures but just 'pass'. test_ha_steady_state_pl depends on them, so HA setup/activation never happens.

2. Teardown uses dpuhost out of scope: in common_setup_teardown, dpuhost is defined inside the for-loop. After yield, config_reload(dpuhost, ...) may reference only the last dpuhost or be undefined if skip_config returned early. Consider iterating all dpuhosts in teardown or moving dpuhost into outer scope.

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[aronovic]

Blocking issues:

1. HA setup fixtures are empty: setup_dash_ha_from_json and activate_dash_ha_from_json in tests/ha/conftest.py are fixtures but just 'pass'. test_ha_steady_state_pl depends on them, so HA setup/activation never happens.
2. Teardown uses dpuhost out of scope: in common_setup_teardown, dpuhost is defined inside the for-loop. After yield, config_reload(dpuhost, ...) may reference only the last dpuhost or be undefined if skip_config returned early. Consider iterating all dpuhosts in teardown or moving dpuhost into outer scope.

Sure, issue 1 is well understood. After the PR that implements those 2 functions gets merged this PR will get updated.
I took care of issue 2 in my latest commit.

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).