Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-2701

On Power catalog is not getting created on OCP4.12

    XMLWordPrintable

Details

    • None
    • False

    Description

      Description of problem:

      On P for latest iib 403361 of OCP 4.12, catalog is not getting created

      Steps to Reproduce

      1. Apply this catalog yaml file with this iib 

      # cat pipe_my_catalog.yaml
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      metadata:
        name: custom-operators
        namespace: openshift-marketplace
      spec:
        sourceType: grpc
        image: quay.io/openshift-pipeline/redhat-operator-index:403361
        displayName: custom-operators
        updateStrategy:
          registryPoll:
            interval: 30m# oc apply -f pipe_my_catalog.yaml
      catalogsource.operators.coreos.com/custom-operators created

      2. Check pods state 

      # oc get pods -n openshift-marketplace | grep custom-operators
      custom-operators-pfbwn                  0/1     CrashLoopBackOff   1 (10s ago)   41s
       

      Actual results:

      On P for latest iib 403361 of OCP 4.12, catalog is not getting created, it goes in CrashLoopBackOff state

      Expected results:

      Catalog should get created and it should be in running state.

      Build Details:

      iib: 403361 OCP 4.12   build date 23-Dec-2022      
      iib: 403619 OCP 4.12   build date 24-Dec-2022  

      Additional linfo (Such as Logs, Screenshots, etc):

      $  oc describe pod custom-operators-v4bzr -n openshift-marketplace
      Name:         custom-operators-v4bzr
      Namespace:    openshift-marketplace
      Priority:     0
      Node:         ppc64le-qe51b-s6cp2-worker-0-vsvc9/192.168.127.52
      Start Time:   Thu, 29 Dec 2022 10:22:03 +0000
      Labels:       olm.catalogSource=custom-operators
                    olm.pod-spec-hash=5d7c5bbdd
      Annotations:  cluster-autoscaler.kubernetes.io/safe-to-evict: true
                    k8s.v1.cni.cncf.io/network-status:
                      [{
                          "name": "openshift-sdn",
                          "interface": "eth0",
                          "ips": [
                              "10.129.3.224"
                          ],
                          "default": true,
                          "dns": {}
                      }]
                    k8s.v1.cni.cncf.io/networks-status:
                      [{
                          "name": "openshift-sdn",
                          "interface": "eth0",
                          "ips": [
                              "10.129.3.224"
                          ],
                          "default": true,
                          "dns": {}
                      }]
                    openshift.io/scc: restricted-v2
                    seccomp.security.alpha.kubernetes.io/pod: runtime/default
      Status:       Running
      IP:           10.129.3.224
      IPs:
        IP:  10.129.3.224
      Containers:
        registry-server:
          Container ID:  cri-o://6aaf26d703b6e77f33f367922d3610844c2dc20802cc88dfa2b8c410a0de1e3b
          Image:         quay.io/openshift-pipeline/redhat-operator-index:403361
          Image ID:      quay.io/openshift-pipeline/redhat-operator-index@sha256:05c911c1b1b8570f61b779ebbe91836475fc19e0a2d39b3f4bf0f16b615bf0e6
          Port:          50051/TCP
          Host Port:     0/TCP
          State:         Waiting
            Reason:      CrashLoopBackOff
          Last State:    Terminated
            Reason:      Error
            Message:     Error: compute digest: compute hash: write tar: open /tmp/cache/cache: permission denied
      Usage:
        opm serve <source_path> [flags]Flags:
            --cache-dir string         if set, sync and persist server cache directory
            --cache-only               sync the serve cache and exit without serving
            --debug                    enable debug logging
        -h, --help                     help for serve
        -p, --port string              port number to serve on (default "50051")
        -t, --termination-log string   path to a container termination log file (default "/dev/termination-log")Global Flags:
            --skip-tls-verify   skip TLS certificate verification for container image registries while pulling bundles
            --use-http          use plain HTTP for container image registries while pulling bundles
            Exit Code:    1
            Started:      Thu, 29 Dec 2022 10:22:48 +0000
            Finished:     Thu, 29 Dec 2022 10:22:49 +0000
          Ready:          False
          Restart Count:  3
          Requests:
            cpu:        10m
            memory:     50Mi
          Liveness:     exec [grpc_health_probe -addr=:50051] delay=10s timeout=5s period=10s #success=1 #failure=3
          Readiness:    exec [grpc_health_probe -addr=:50051] delay=5s timeout=5s period=10s #success=1 #failure=3
          Startup:      exec [grpc_health_probe -addr=:50051] delay=0s timeout=1s period=10s #success=1 #failure=15
          Environment:  <none>
          Mounts:
            /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-95j8r (ro)
      Conditions:
        Type              Status
        Initialized       True
        Ready             False
        ContainersReady   False
        PodScheduled      True
      Volumes:
        kube-api-access-95j8r:
          Type:                    Projected (a volume that contains injected data from multiple sources)
          TokenExpirationSeconds:  3607
          ConfigMapName:           kube-root-ca.crt
          ConfigMapOptional:       <nil>
          DownwardAPI:             true
          ConfigMapName:           openshift-service-ca.crt
          ConfigMapOptional:       <nil>
      QoS Class:                   Burstable
      Node-Selectors:              kubernetes.io/os=linux
      Tolerations:                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                                   node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                                   node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
      Events:
        Type     Reason          Age               From               Message
        ----     ------          ----              ----               -------
        Normal   Scheduled       53s               default-scheduler  Successfully assigned openshift-marketplace/custom-operators-v4bzr to ppc64le-qe51b-s6cp2-worker-0-vsvc9
        Normal   AddedInterface  51s               multus             Add eth0 [10.129.3.224/23] from openshift-sdn
        Normal   Pulled          50s               kubelet            Successfully pulled image "quay.io/openshift-pipeline/redhat-operator-index:403361" in 783.501286ms
        Normal   Pulled          48s               kubelet            Successfully pulled image "quay.io/openshift-pipeline/redhat-operator-index:403361" in 365.70392ms
        Normal   Pulled          31s               kubelet            Successfully pulled image "quay.io/openshift-pipeline/redhat-operator-index:403361" in 350.489219ms
        Normal   Created         9s (x4 over 50s)  kubelet            Created container registry-server
        Normal   Started         9s (x4 over 50s)  kubelet            Started container registry-server
        Normal   Pulling         9s (x4 over 51s)  kubelet            Pulling image "quay.io/openshift-pipeline/redhat-operator-index:403361"
        Normal   Pulled          9s                kubelet            Successfully pulled image "quay.io/openshift-pipeline/redhat-operator-index:403361" in 317.599122ms
        Warning  BackOff         3s (x9 over 47s)  kubelet            Back-off restarting failed container
      
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            vaaynure Varsha Aaynure
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: