-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[lldpmgrd] Fix lldpmgrd issue where it sets the lldp system name to None #11907
base: master
Are you sure you want to change the base?
Conversation
- Only check hostname field in key DEVICE_METADATA|localhost of configDB - If hostname does not exist, don't set lldp system name Signed-off-by: Zhenggen Xu <[email protected]>
|
Signed-off-by: Zhenggen Xu <[email protected]>
/azpw run |
/AzurePipelines run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add UT
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
[lldpmgrd] Fix lldpmgrd issue where it sets the lldp system name to None
Signed-off-by: Zhenggen Xu [email protected]
Why I did it
lldpmgrd could set the system name to None incorrectly, which lead to peer to have wrong lldp information.
How I did it
Fix the lldpmgrd.
How to verify it
Before fix:
If loading below config:
lldp will set the system name to None, see syslog:
After the fix, if loading the same config:
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)