[ieee802_1ab]Ensuring that the LLDP_system_data is non-empty before getting field from it.#135
Open
sdddean wants to merge 1 commit intosonic-net:masterfrom
Open
[ieee802_1ab]Ensuring that the LLDP_system_data is non-empty before getting field from it.#135sdddean wants to merge 1 commit intosonic-net:masterfrom
sdddean wants to merge 1 commit intosonic-net:masterfrom
Conversation
…field from it. Signed-off-by: sundandan <sundandan@asterfusion.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: sundandan sundandan@asterfusion.com
What I did
Add a non-empty protection before getting field form local_chassis_date.
Why I did it
As the logic in sonic-dbsyncd, there will be no 'LLDP_LOC_CHASSIS' table in APP DB until we establish neighbor relationships with LLDP neighbors.
When there is no 'LLDP_LOC_CHASSIS' table in APP DB, walk node .1.0.8802.1.1.2.1.3 will led to error log:
How I verified it
The error log described above does not appear anymore.