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

[4.18] remove phc2sys `-w` option

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Removed obsolete '-w' phc2sys option in the reference T-GM configuration
    • Enhancement
    • In Progress
    • Hide
      02/20: This will need to wait for 2025-02-25 until https://issues.redhat.com/browse/RHEL-69138 ships out
      01/30: PR posted pending review
      Show
      02/20: This will need to wait for 2025-02-25 until https://issues.redhat.com/browse/RHEL-69138 ships out 01/30: PR posted pending review

      Note - this is a clone of the original https://issues.redhat.com/browse/OCPBUGS-44603

      Its purpose is to track the reference configuration changes in the ZTP repository and the documentation updates associated with this change

      Description of problem:

      The doc[1] recommended  to configure phc2sysOpts with the following parameter '-w'.

      phc2sysOpts: -r -u 0 -m -w -N 8 -R 16 -S 2 -s ens2f0 -n 24 

      The issue is that when links of master or slave is down, the phc2sys is waiting for ptp4l unless any link is up.

      In the T-GM node from the 'Figure 1. PTP nodes in the network' of the doc[2], ts2phc seems to update PHC directly and it seems to be referred by phc2sys. I don't think of way why the ptp4l is in the middle of the process of phc2sys. In other word, phc2sys seems to can synchronize without ptp4l. Nevertheless, the phc2sys is waiting for ptp4l with the following log.

       

      2024-11-13T07:25:36.154544564Z phc2sys[1288096.888]: [ptp4l.0.config] Waiting for ptp4l... 

       

       

      Is this expected behavior? why the ptp4l is needed for synchroniation of system clock(phc2sys) even on T-GM node?

      The partner 'Samsung' wants to implementation T-GM without any links of T-BC or T-OC up. They are speaking the use case(situation) may be a maintenance or implementation step.

      [1] Configuring dynamic leap seconds handling for PTP grandmaster clocks
      https://docs.openshift.com/container-platform/4.14/networking/ptp/configuring-ptp.html#ptp-configuring-dynamic-leap-seconds-handling-for-tgm_configuring-ptp

      [2] Elements of a PTP domain
      https://docs.openshift.com/container-platform/4.14/networking/ptp/about-ptp.html#ptp-elements_about-ptp

       

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

      OCP 4.14z and later.    

      Steps to Reproduce:

      1. Configure T-GM without any links to T-BC/O-BC.
      
      2. phc2sys is stuck with the following log.
      ~~~
      2024-11-13T07:25:36.154544564Z phc2sys[1288096.888]: [ptp4l.0.config] Waiting for ptp4l...
      ~~~  

      Actual results:

      - phc2sys was stuck to synchronize system clock

      Expected results:

      - phc2sys synchronizes system clock without ptp4l.

              vgrinber@redhat.com Vitaly Grinberg
              rhn-support-hyupark HyunYick Park
              Hen Shay Hassid Hen Shay Hassid
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: