Skip to content

[action] [PR:8909] [dualtor] Leave icmp_responder running on dualtor topology#9064

Merged
mssonicbld merged 1 commit intosonic-net:202205from
mssonicbld:cherry/202205/8909
Jul 21, 2023
Merged

[action] [PR:8909] [dualtor] Leave icmp_responder running on dualtor topology#9064
mssonicbld merged 1 commit intosonic-net:202205from
mssonicbld:cherry/202205/8909

Conversation

@mssonicbld
Copy link
Copy Markdown
Collaborator

ADO#: 24560210

Description of PR

Summary:
Fixes # (issue)
Enforcing same behavior on dualtor, dualtor-aa and dualtor-mixed topology.

sign-off: Jing Zhang [email protected]

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

To enforce same behavior on dualtor, dualtor-aa, dualtor-mixed testbeds.

How did you do it?

How did you verify/test it?

Verified on dualtor testbed.

Any platform specific information?

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

Documentation

…-net#8909)

Summary:
Fixes # (issue)
Enforcing same behavior on dualtor, dualtor-aa and dualtor-mixed topology.

sign-off: Jing Zhang [email protected]
@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Original PR: #8909

@mssonicbld mssonicbld merged commit f162dd8 into sonic-net:202205 Jul 21, 2023
@mssonicbld mssonicbld deleted the cherry/202205/8909 branch February 4, 2024 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants