Fix the ignore pattern - leapsecond file expired warning#19332
Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom Jul 3, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jul 3, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
Collaborator
|
Cherry-pick PR to 202411: #19356 |
11 tasks
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jul 3, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
Collaborator
|
Cherry-pick PR to 202505: #19365 |
11 tasks
yejianquan
pushed a commit
that referenced
this pull request
Jul 3, 2025
…9365) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Co-authored-by: ShiyanWangMS <[email protected]>
11 tasks
Collaborator
|
Cherry-pick PR to msft-202405: Azure/sonic-mgmt.msft#499 |
mssonicbld
added
Included in msft-202405 Branch
and removed
Created PR to msft-202405 Branch
labels
mssonicbld
pushed a commit
that referenced
this pull request
Jul 7, 2025
What is the motivation for this PR?
The following syslog should be ignored.
2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago
How did you do it?
Change the ignore pattern
How did you verify/test it?
Verify with physical testbed
11 tasks
Collaborator
|
Cherry-pick PR to msft-202503: Azure/sonic-mgmt.msft#504 |
sdszhang
pushed a commit
to sdszhang/sonic-mgmt
that referenced
this pull request
Aug 2, 2025
Code sync sonic-net/sonic-mgmt:202411 => 202412 ``` * 3124d52 (HEAD -> code-sync-202412, origin/code-sync-202412) r12f 250710:1626 - Merge remote-tracking branch 'base/202411' into code-sync-202412 |\ | * b1b95dc (base/202411) zitingguo-ms 250513:1848 - Fix PortChannel name matching in verify_attr_change to handle leading spaces (sonic-net#18301) | * 7461bf3 wrideout-arista 250604:1542 - Determine if the eos switch is running in multiagent mode, and stop/start the (sonic-net#18748) | * 4346afd Dashuai Zhang 250411:0103 - update d18u8s4 PT0 ASN to 4 bytes (sonic-net#17888) | * de1b1b4 Ryangwaite 250709:1028 - Skip multi-hop upgrade tests on non-T0 testbeds (sonic-net#19078) (sonic-net#19326) | * 573d42d Cong Hou 250709:0232 - Update the skip for test test_qos_dscp_mapping.py (sonic-net#19381) | * 3eb65b9 Yawen 250708:1743 - Unskip test_qos_sai for dualtor-aa-64-breakout (sonic-net#19363) | * f0c9705 Cong Hou 250707:2351 - xfail generic hash test on dualtor (sonic-net#19383) | * d378110 eyakubch 250707:0546 - Reduce flakiness of test_l2_configure.py. (sonic-net#18831) | * 043dba8 ShiyanWangMS 250703:0935 - Fix the ignore pattern - leapsecond file expired warning (sonic-net#19332) | * 92af38f zitingguo-ms 250703:1958 - Unskip testQosSaiHeadroomPoolWatermark on t0-d18u8s4 (sonic-net#19287) (sonic-net#19342) | * 0b7e4de Chuan Wu 250704:0334 - Add background traffic for test_pfc_pause_extra_lossless test (sonic-net#19218) ```
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: opcoder0 <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: Guy Shemesh <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…9332) What is the motivation for this PR? The following syslog should be ignored. 2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago How did you do it? Change the ignore pattern How did you verify/test it? Verify with physical testbed Signed-off-by: Yael Tzur <[email protected]>
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
6 participants
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:
The ignore pattern for leapsecond file expired warning is incorrect.
Type of change
Back port request
Approach
What is the motivation for this PR?
The following syslog should be ignored.
2025 Jul 1 09:30:14.223456 bjw2-can-8102-1 ERR ntpd[224326]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 4 days ago
How did you do it?
Change the ignore pattern
How did you verify/test it?
Verify with physical testbed
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation