Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: enable T2 auto health check #16825

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cyw233
Copy link
Contributor

@cyw233 cyw233 commented Feb 6, 2025

Description of PR

Enable T2 auto health check and add running container info to return data.

Summary:
Fixes # (issue) Microsoft ADO 30293537

Type of change

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

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405
  • 202411

Approach

What is the motivation for this PR?

We want to enable T2 auto health check as we have now supported T2 auto recover.

How did you do it?

How did you verify/test it?

Any platform specific information?

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

Documentation

@mssonicbld
Copy link
Collaborator

/azp run

@cyw233 cyw233 marked this pull request as ready for review February 6, 2025 08:58
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Comment on lines -221 to -228
# TODO: Refactor the following code to specify a "leader" T2 Testbed and skip the check on "followers"
# Retrieve the basic facts of the DUTs
if self.is_multi_asic:
errmsg = "Not support to perform checks on multi-asic DUT now."
logger.info(errmsg)

raise SkipCurrentTestbed(errmsg)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we remove this skip logic, will multi_asic Testbed be affected? I remember previously multi_asic testbed can't run some ansible module(like get dut facts, bgp facts). I'm not quite sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The multi_asic Testbed won't be affected. Please see the comment here: #15836 (comment)

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.

3 participants