Loading...

XML

Word

Printable

Type: Bug
Resolution: Can't Do
Priority: Major
Fix Version/s: None
Affects Version/s: 4.20
Component/s: Networking / ptp
Labels:
- Telco
- Telco:RAN
- ptp
- ptp-boundary-clock
- t-bc

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Important
Regression:
None
Latest Status Summary:
2025-10-27 [dev]: It's a typical behavior of ptp4l source, won't fix

Target Backport Versions:
None
Target Version:

4.20.z
Release Blocker:
None
Sprint:
CNF RAN Sprint 278, CNF RAN Sprint 279
sprint_count:
2

RH Private Keywords:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    After soft rebooting the PTP node the PTP service is slow to lock; one hour~

Version-Release number of selected component (if applicable):

    ptp-operator.v4.20.0-202510172045

How reproducible:

    100%

Steps to Reproduce:

    1.Reboot the node; sudo reboot.
    2.Watch & wait for the clock to report 'Locked'; "oc -n openshift-ptp exec ds/linuxptp-daemon -c cloud-event-proxy -- curl -s localhost:9091/metrics | grep clock"

Actual results:

     Clock entered 'Locked' after an hour

Expected results:

    Clock enters 'Locked' within minutes

Additional info:

Assignee:: Vitaly Grinberg

Reporter:: Daniel Popsuevich

Need Info From:: None

Contributors:: None

QA Contact:: Yang Liu

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/10/22 2:21 PM

Updated:: 2025/10/29 10:08 AM

Resolved:: 2025/10/29 8:00 AM