-
Notifications
You must be signed in to change notification settings - Fork 753
[generic_config_updater] Add diagnostic logging for vlanintf_validato… #4105
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
Open
DavidZagury
wants to merge
4
commits into
sonic-net:master
Choose a base branch
from
DavidZagury:master_service_validatior_log
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[generic_config_updater] Add diagnostic logging for vlanintf_validato… #4105
DavidZagury
wants to merge
4
commits into
sonic-net:master
from
DavidZagury:master_service_validatior_log
+93
−4
Conversation
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
…r failures Add enhanced error logging to diagnose vlanintf_validator failures when flushing neighbor entries for deleted VLAN interface IPs. These minimal logging additions only activate on errors, providing zero overhead during normal operation while enabling root cause analysis when the validator fails.
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
volodymyrsamotiy
approved these changes
Nov 3, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
4ee08fe to
44b049d
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
…r failures
Add enhanced error logging to diagnose vlanintf_validator failures when flushing neighbor entries for deleted VLAN interface IPs.
These minimal logging additions only activate on errors, providing zero overhead during normal operation while enabling root cause analysis when the validator fails.
This could help in the investigatation of sonic-net/sonic-buildimage#23680
What I did
Added diagnostic logging to
vlanintf_validatorto identify the root cause when neighbor flush operations fail during VLAN interface IP removal. Previously, the validator would fail silently with only a generic error message, making it impossible to diagnose the actual failure reason.How I did it
Enhanced
command_wrapper()function to:capture_output=TrueAdded error logging in
vlanintf_validator()to:Updated unit tests in
service_validator_test.pyto reflect the original command formatHow to verify it
Normal operation (no errors):
Error scenario:
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)