-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.z
-
None
-
None
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Using the ntpfailover plugin, our tests simulate a loss of GNSS and are able to see that chronyd successfully starts syncing. On simulating the recovery, however, phc2sys fails to start again and repeating logs about a missing config file are present. The problem seems to disappear after the test, possibly because of profiles being loaded again? The change for this scenario is just the ts2phc holdover, the phc2sysOpts remain the same.
Version-Release number of selected component (if applicable):
ptp-operator.v4.18.0-202601151027
How reproducible:
4/4 attempts to test
Steps to Reproduce:
1. Have ntpfailover config successfully syncing from GNSS
2. Simulate GNSS loss and failover to NTP
3. Simulate GNSS recovery and notice lack of phc2sys lock
Actual results:
phc2sys does not lock and cannot start due to missing config
Expected results:
phc2sys locks successfully after GNSS is restored
Additional info:
- depends on
-
OCPBUGS-66971 backport linuxptp-daemon to 4.19
-
- Verified
-
- links to