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

In OCL. Cannot install extensions

XMLWordPrintable

    • Important
    • No
    • 5
    • MCO Sprint 268
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When we install extensions in a cluster using OCL, the build fails reporting this error
      
      Error: building at STEP "RUN --mount=type=bind,from=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8427698b9f2f1829b7ce4ca220d4278dcdf2c51f922c312d5571cce1f6b0d9a7,source=/,target=/tmp/mco-extensions/os-extensions-content,bind-propagation=rshared,rw,z echo -e "[coreos-extensions]\nenabled=1\nmetadata_expire=1m\nbaseurl=/tmp/mco-extensions/os-extensions-content/usr/share/rpm-ostree/extensions/\ngpgcheck=0\nskip_if_unavailable=False" > /etc/yum.repos.d/coreos-extensions.repo &&     chmod 644 /etc/yum.repos.d/coreos-extensions.repo &&     extensions="usbguard krb5-workstation libkadm5 kernel-devel kernel-headers kata-containers NetworkManager-libreswan libreswan crun-wasm sysstat" &&     echo "Installing extension packages: $extensions" &&     rpm-ostree install $extensions &&     rm /etc/yum.repos.d/coreos-extensions.repo": resolving mountpoints for container "d3a95a293456378014ff5030a1479a3ea95a6d87ed01066aebfcca474d1b634f": setting up overlay of "/home/build/.local/share/containers/storage/vfs/dir/56ea6acb37115a17b8188bc2601914e9fe64077ed0a70d0a4deb5554c56ad23b": mount overlay:/var/tmp/buildah3838130017/mounts3684384049/overlay/2916328100/merge, data: lowerdir=/home/build/.local/share/containers/storage/vfs/dir/56ea6acb37115a17b8188bc2601914e9fe64077ed0a70d0a4deb5554c56ad23b,upperdir=/var/tmp/buildah3838130017/mounts3684384049/overlay/2916328100/upper,workdir=/var/tmp/buildah3838130017/mounts3684384049/overlay/2916328100/work,userxattr: invalid argument
      time="2025-02-20T11:14:00Z" level=debug msg="shutting down the store"
      time="2025-02-20T11:14:00Z" level=debug msg="exit status 125"
      
      
      
          

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

      4.18
      
      Using IPI on AWS
      
          

      How reproducible:

      Always
          

      Steps to Reproduce:

          1. Enable OCL in the worker pool
          2. Create a MC to  install the extensions once the OCL has been enabled
      
      apiVersion: machineconfiguration.openshift.io/v1
      kind: MachineConfig
      metadata:
        creationTimestamp: "2025-02-20T11:10:44Z"
        generation: 1
        labels:
          machineconfiguration.openshift.io/role: worker
        name: tc-56131-all-extensions-2
        resourceVersion: "56510"
        uid: 61108c26-a898-451b-83c8-860c403e870f
      spec:
        config:
          ignition:
            version: 3.1.0
        extensions:
        - usbguard
        - kerberos
        - kernel-devel
        - sandboxed-containers
        - ipsec
        - wasm
        - sysstat
      
      
      
          

      Actual results:

      The build fails reporting the error mentioned above
      
      
      $ omc get pods -n openshift-machine-config-operator
      NAME                                                             READY   STATUS    RESTARTS   AGE
      build-mosc-worker-b7665c0a2f36edaf069fa87f45553328-5mcjr         0/2     Error     0          2h
      build-mosc-worker-b7665c0a2f36edaf069fa87f45553328-cjpc4         0/2     Error     0          2h
      build-mosc-worker-b7665c0a2f36edaf069fa87f45553328-nsqnm         0/2     Error     0          2h
      build-mosc-worker-b7665c0a2f36edaf069fa87f45553328-rw2jh         0/2     Error     0          2h
      kube-rbac-proxy-crio-ip-10-0-18-151.us-east-2.compute.internal   1/1     Running   3          3h
      
          

      Expected results:

      The image should be built without errors and properly deployed on the nodes
          

      Additional info:

      
          

              dkhater@redhat.com Dalia Khater
              sregidor@redhat.com Sergio Regidor de la Rosa
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: