-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.13
-
No
-
False
-
-
Description of problem:
The linuxptp-daemon container image ships its own version of the leap-seconds.list file, overwriting the one provided by the tzdata package [1][2]. This file has an expiration date of June 28, 2023. After this expiration date, ts2phc fails to parse the file and shows the following error message in the logs: nmea: unable to find utc time in leap second table This errors prevents ts2phc from working, since it discards all information received from the GNSS device file. [1] - https://github.com/openshift/linuxptp-daemon/blob/master/extra/leap-seconds.list [2] - https://github.com/openshift/linuxptp-daemon/blob/master/Dockerfile#L26
Version-Release number of selected component (if applicable):
Seen on OpenShift 4.13.x
How reproducible:
Always
Steps to Reproduce:
1. podman run -it quay.io/openshift/origin-ptp:4.13 sh 2. cat /usr/share/zoneinfo/leap-seconds.list
Actual results:
Expiration date shown in the file is: # Updated through IERS Bulletin C64 # File expires on: 28 June 2023 # #@ 3896899200
Expected results:
Expiration date should be the same as the file provided by https://www.ietf.org/timezones/data/leap-seconds.list: # Updated through IERS Bulletin C65 # File expires on: 28 December 2023 # #@ 3912710400
Additional info:
- blocks
-
OCPBUGS-15897 leap-seconds.list file included as part of linuxptp-daemon container expired on June 28, 2023
- Closed
- is cloned by
-
OCPBUGS-15897 leap-seconds.list file included as part of linuxptp-daemon container expired on June 28, 2023
- Closed
- is related to
-
OCPBUGS-25939 T-GM ts2phc IERS Bulletin expired December the 28th
- Closed
- relates to
-
RFE-5041 PTP Leap Seconds maintenance in connected and disconnected environment
- Under Review
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update
- mentioned in
-
Page Loading...