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

linuxptp-daemon-container stuck in CrashLoopBackOff upon deployment on GM config

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Back-off restarting failed container linuxptp-daemon-container in pod linuxptp-daemon- on spoke with GM config.

SNO environment:
$ oc get clusterversions.config.openshift.io 
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.0-0.nightly-2023-08-08-094653   True        False         71m     Cluster version is 4.14.0-0.nightly-2023-08-08-094653
$ oc get csv -n openshift-ptp ptp-operator.v4.14.0-202308050144 
NAME                                DISPLAY        VERSION               REPLACES   PHASE
ptp-operator.v4.14.0-202308050144   PTP Operator   4.14.0-202308050144              Succeeded

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

      4.14.0-202308050144

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install ptp-operator from stage
2. Check openshift-ptp pods:  
[kni@registry.ran-vcl01 ~]$ oc get pods -n openshift-ptp
NAME                            READY   STATUS             RESTARTS      AGE
linuxptp-daemon-9c4bs           2/3     CrashLoopBackOff   9 (64s ago)   30m
ptp-operator-5fbb7c7b85-kb2h8   1/1     Running            2             81m
[kni@registry.ran-vcl01 ~]$ 

      Actual results:

      linuxptp-daemon fails to start with CrashLoopBackOff

      Expected results:

      linuxptp-daemon starts successfully

      Additional info:

       

            aputtur@redhat.com Aneesh Puttur
            bblock@redhat.com Bonnie Block
            Bonnie Block Bonnie Block
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: