-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
Yes
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
Two ptp GM environments are not able to connect to GPS source. These environments were working before installing newer builds of ptp-operator.
helix59: ptp-operator.v4.19.0-202504031615 <- "GM-GNSS interface is not yet identified"
helix60: ptp-operator.v4.19.0-202504030332 <- "GM-GNSS interface is not yet identified"
helix65: ptp-operator.v4.19.0-202503290310 <- this env is working
linuxptp-daemon logs shows:
I0404 16:50:42.146422 1253725 event.go:320] GM-GNSS interface is not yet identified, gm state reporting delayed.
and
ts2phc[99489.462]: [ts2phc.2.config:3] failed to open nmea source /gpsd/data ts2phc[99489.630]: [ts2phc.2.config:7] nmea: no valid rmc fix
Version-Release number of selected component (if applicable):
ptp-operator.v4.19.0-202504030332 ptp-operator.v4.19.0-202504031615
How reproducible:
100%
Steps to Reproduce:
1. Deploy SNO with ptp operator in a GM environment
2. View linuxptp-daemon log
Actual results:
I0404 16:50:42.146422 1253725 event.go:320] GM-GNSS interface is not yet identified, gm state reporting delayed.
and
ts2phc[99489.462]: [ts2phc.2.config:3] failed to open nmea source /gpsd/data ts2phc[99489.630]: [ts2phc.2.config:7] nmea: no valid rmc fix
Expected results:
log shows gnss and gm states
Additional info:
- duplicates
-
-
- Closed
-
- links to
-
RHEA-2024:11038
OpenShift Container Platform 4.19.z bug fix update
