[202411] Ignore loganaylzer errors about the leapsecond file being expired #19285
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
Depending on the image that is running, when it was built, and what version of packages were used, the leapsecond fil might be expired. Ignore errors from ntpd about it, since the only functional impact that it might cause is that if there is a leapsecond, the system clock will be off by a second for a little bit until it gets corrected. Signed-off-by: Saikrishna Arcot <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
rminnikanti
approved these changes
Jul 2, 2025
|
@saiarcot895 there is already a ignore regex at line309 which isn't working. Pasted here: # ignore leap second file NTP daemon (ntpd) is using has passed its expiration date
r, ".* ERR ntpd\[\d*\]:.*leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired.*"We can either remove it or fix it and make it work. Also, is this change only being made to 202411 branch? |
|
We are seeing this issue in 202503 release branch as well. Can you please add Request label for 202503 branch? |
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.
Description of PR
Summary:
Fixes sonic-net/sonic-buildimage#23142
Fixes sonic-net/sonic-buildimage#17653
Fixes sonic-net/sonic-buildimage#11327
Type of change
Back port request
Approach
What is the motivation for this PR?
Depending on the image that is running, when it was built, and what version of packages were used, the leapsecond file might be expired. Ignore errors from ntpd about it, since the only functional impact that it might cause is that if there is a leapsecond, the system clock will be off by a second for a little bit until it gets corrected.
How did you do it?
Add a loganalyzer pattern to ignore such error messages.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation