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

chronyd.service fails to start on some nodes

    XMLWordPrintable

Details

    • Important
    • No
    • CNF RAN Sprint 247, CNF RAN Sprint 248
    • 2
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • 10/24: 4.14.z fcast pending triage

    Description

      Description of problem:

      When configuring NTP some nodes have issues

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

      OCP: 4.14.0-rc6
      ACM: 2.9.0-187
      MCE: 2.4.0-198
      GITOPS: 1.10.0

      How reproducible:

       

      Steps to Reproduce:

      1. Add additionalNTPSources to site-config
      2. Deploy spoke cluster with ztp gitops
      3. check timedatectl & chronyd status on all nodes
      

      Actual results:

      oc debug node/openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com
      Starting pod/openshift-worker-1kni-qe-6labengrdu2redhatcom-debug-8lxrp ...
      To use host binaries, run `chroot /host`
      Pod IP: 10.1.220.24
      If you don't see a command prompt, try pressing enter.
      sh-4.4# chroot /host
      sh-5.1# timedatectl
                     Local time: Mon 2023-10-16 14:52:05 UTC
                 Universal time: Mon 2023-10-16 14:52:05 UTC                                                                    
                       RTC time: Mon 2023-10-16 14:52:05                        
                      Time zone: UTC (UTC, +0000)
      System clock synchronized: no
                    NTP service: inactive                   
                RTC in local TZ: no
      
      sh-5.1# systemctl status chronyd
      × chronyd.service - NTP client/server
           Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; preset: enabled)
          Drop-In: /usr/lib/systemd/system/chronyd.service.d
                   └─platform-chrony.conf
           Active: failed (Result: timeout) since Mon 2023-10-16 13:36:26 UTC; 1h 20min ago
             Docs: man:chronyd(8)
                   man:chrony.conf(5)
              CPU: 58msOct 16 13:34:56 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com chronyd[1915]: Loaded seccomp filter (level 2)
      Oct 16 13:34:56 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com systemd[1]: chronyd.service: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /run/chrony/chronyd.pid
      Oct 16 13:34:56 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com systemd[1]: chronyd.service: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /run/chrony/chronyd.pid
      Oct 16 13:35:09 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com chronyd[1915]: Source 104.194.8.227 offline
      Oct 16 13:35:09 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com chronyd[1915]: Source 104.167.241.253 offline
      Oct 16 13:35:09 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com chronyd[1915]: Source 10.11.160.238 offline
      Oct 16 13:36:26 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com systemd[1]: chronyd.service: start operation timed out. Terminating.
      Oct 16 13:36:26 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com chronyd[1915]: chronyd exiting
      Oct 16 13:36:26 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com systemd[1]: chronyd.service: Failed with result 'timeout'.
      Oct 16 13:36:26 openshift-worker-1.kni-qe-6.lab.eng.rdu2.redhat.com systemd[1]: Failed to start NTP client/server.

      Expected results:

      chronyd started successfully and time synced with NTP

      Additional info:

      Other nodes 3 masters and another worker has NTP configured successfully. worker-1 has correct /etc/chrony.conf from the machine config.

      Attachments

        Issue Links

          Activity

            People

              vgrinber@redhat.com Vitaly Grinberg
              agurenko@redhat.com Alexander Gurenko
              Joshua Clark Joshua Clark
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: