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

[action] [PR:17486] Fix syncd_request_shutdown coredump in config reload on KVM sonic #17564

Merged
merged 1 commit into from
Dec 19, 2023

Conversation

mssonicbld
Copy link
Collaborator

Why I did it

The issue is related to #16812. Process syncd does not run in the container gbsyncd on kvm sonic with default hwsku.

Work item tracking
  • Microsoft ADO : 26151608

How I did it

If syncd has not run in container gbsyncd, it is not needed to trigger graceful shudown of syncd.

How to verify it

None of syncd_request_shutdown coredump in config reload on KVM sonic

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

…nic-net#17486)

The issue is related to sonic-net#16812. Process syncd does not run in the container gbsyncd on kvm sonic with default hwsku.

Microsoft ADO : 26151608

How I did it
If syncd has not run in container gbsyncd, it is not needed to trigger graceful shudown of syncd.

How to verify it
None of syncd_request_shutdown coredump in config reload on KVM sonic
@mssonicbld
Copy link
Collaborator Author

Original PR: #17486

@mssonicbld mssonicbld merged commit 7f03584 into sonic-net:202305 Dec 19, 2023
17 checks passed
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