Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35024

PTP Boundary HA configuration cannot handle spaced empty Phc2SysOpts and ptp4lOpts with

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.16
    • Networking / ptp
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-33524. The following is the description of the original issue:
      —
      Description of problem:

         After creating boundary clock configurations and boundary ha configuration, pod's log shows that ptp4l cannot be started with no interface specified error.

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

      How reproducible:

      Steps to Reproduce:

          1. Create BC1 config
    2. Create BC2 config
    3. Create BC HA config
    4. Delete pod for a good measure
    5. Check the pod's linuxptp-daemon-container logs

      Actual results:

          I0510 12:12:28.365179 3095645 daemon.go:768] ptp4l cmd: /bin/chrt -f 10 /usr/sbin/ptp4l -f /var/run/ptp4l.2.config    -m                                                                                      [20/1870]I0510 12:12:28.365661 3095645 daemon.go:698] ptp4l[1715343148]:[ptp4l.2.config] PTP_PROCESS_STATUS:1
no interface specified
...
E0510 12:12:28.367660 3095645 daemon.go:856] CmdRun() error waiting for ptp4l: exit status 255

      Expected results:

          Both ptp4l processes started successfully

      Additional info:

          Same error for the second ptp4l configuration

              aputtur@redhat.com Aneesh Puttur
              openshift-crt-jira-prow OpenShift Prow Bot
              Hen Shay Hassid Hen Shay Hassid
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: