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

oc mirror command produces no output when executed on RHEL 8 with /tmp mounted as noexec in /etc/fstab

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • CLID Sprint 274, CLID Sprint 275, CLID Sprint 276, CLID Sprint 277
    • 4
    • In Progress
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      Description of problem:

      When running the oc mirror command (version 4.19.0) on a RHEL 8 system where the /tmp directory is mounted with the noexec option in /etc/fstab, the command fails to produce any output. This issue prevents the successful mirroring of container images as configured. The noexec mount option on /tmp likely restricts the execution of temporary files or scripts required by the oc mirror process, causing it to fail silently. The issue was observed during a dry-run execution with a specific configuration file and workspace.

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

      oc mirror version: Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.19.0-202507081507.p0.gf364aec.assembly.stream.el9-f364aec", GitCommit:"f364aec3fc13fad183ff85ad40b6c861964c483e", GitTreeState:"clean", BuildDate:"2025-07-09T00:30:17Z", GoVersion:"go1.23.9 (Red Hat 1.23.9-1.module+el8.10.0+23162+9223a61a) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}

      How reproducible:

          

      Steps to Reproduce:

      1. Set up a RHEL 8 system.
      
      2. Ensure the /tmp directory is mounted with the noexec option in /etc/fstab. You can verify this by running:
      
      cat /etc/fstab| grep -i tmp
      /dev/mapper/VG00-tmp                            /tmp             xfs      defaults,nodev,nosuid,noexec       1 2
      
      
      3. Install oc mirror version 4.19.0 (specific build: GitVersion "4.19.0-202507081507.p0.gf364aec.assembly.stream.el9-f364aec")
      
      4. Create or obtain a valid oc mirror configuration file (e.g., redhat-operator-mirror-4.16.yaml) and place it in a directory such as /apps/srvquay/mirror-operators/redhat-operator/
      
      5. Ensure a workspace directory exists (e.g., /apps/srvquay/mirror-operators/redhat-operator).
      
      6. Run the following oc mirror command:
      
      oc-mirror -c /apps/srvquay/mirror-operators/redhat-operator/redhat-operator-mirror-4.16.yaml --workspace file:///apps/srvquay/mirror-operators/redhat-operator docker://cbq-svp-rosquay1.cbq.com.qa/rosquay/redhat-operator --v2 --dry-run
      
      
      7. Observe that the command produces no output and exits silently.

      Actual results:

        No result are produced

      Expected results:

         A list of images and operator catalogs that would be mirrored from the source to the destination

      Additional info:

          

              rdossant Rafael Fonseca dos Santos
              rh-ee-awadekar Aditi Wadekar
              None
              None
              Nidan Gavali Nidan Gavali
              None
              Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: