Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-40312

OpenShift CNV Validation Images for RHOCP 4.14 and 4.15 contain wrong architecture executable code

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • CNV v4.17.0
    • CNV v4.15.0, CNV v4.14.4
    • CNV Network
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.17.0.rhel9-60
    • ---
    • ---
    • Moderate
    • No

      Description of problem:

      I am working with a Partner, Tigera, who filed a case with Cert-Ops  (03781209) where they're trying to run the CNV conformance tests for RHOCP v4.14 and v4.15 (versions 1.0.0 and 1.1.0 respectively), but it turns out that the nominally AMD64 images in quay.io/kubevirt/conformance:v1.1.0 and quay.io/kubevirt/conformance:v1.1.0 are really ARM64 images.
      
      Here's what I get when I pull the 1.0.0 image and examine it:
      
      
      ryzen1 (unshared)> uname -a
      Linux ryzen1.narfnet.com 4.18.0-513.18.1.el8_9.x86_64 #1 SMP Thu Feb 1 03:51:05 EST 2024 x86_64 x86_64 x86_64 GNU/Linux
      rryzen1 (unshared)> podman pull quay.io/kubevirt/conformance:v1.0.0
      Trying to pull quay.io/kubevirt/conformance:v1.0.0...
      Getting image source signatures
      Copying blob 6dfe0c8b5a12 done  
      Copying blob 9fb3436fe506 done  
      Copying blob 5f80a38cb015 done  
      Copying blob c850358c93a0 skipped: already exists  
      Copying blob 00b08c26e5bb skipped: already exists  
      Copying config ec92ca26de done  
      Writing manifest to image destination
      ec92ca26de11c9eba82b8d4f46ff58c0e3d9eb11c599679c7be759b973ab7424
      ryzen1 (unshared)> cd $(podman image mount quay.io/kubevirt/conformance:v1.0.0)/usr/bin
      /home/jfrancin/.local/share/containers/storage/overlay/b320cc0076d112ad19399b934017e6d599b701188558ab5f1bea1fd384d6e521/merged/usr/bin
      ryzen1 (unshared)> ls
      conformance  c_rehash  go_default_test  openssl
      ryzen1 (unshared)> file conformance
      conformance: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, with debug_info, not stripped
      
      And with the 1.1.0 image:
      
      ryzen1 (unshared)> uname -a
      Linux ryzen1.narfnet.com 4.18.0-513.18.1.el8_9.x86_64 #1 SMP Thu Feb 1 03:51:05 EST 2024 x86_64 x86_64 x86_64 GNU/Linux
      ryzen1 (unshared)> podman pull quay.io/kubevirt/conformance:v1.1.0
      Trying to pull quay.io/kubevirt/conformance:v1.1.0...
      Getting image source signatures
      Copying blob b003b463d750 done  
      [...]
      Copying config 29b888b1cd done  
      Writing manifest to image destination
      29b888b1cdfda4b19aaf7b4bec57f8181f95ffce162c9cf65be4491894ce3118
      ryzen1 (unshared)> cd $(podman image mount quay.io/kubevirt/conformance:v1.1.0)/usr/bin
      /home/jfrancin/.local/share/containers/storage/overlay/32a10deae5be9294ddcb98ea86e5fe42b475ad377755b2e9afedb8f2e51ab12c/merged/usr/bin
      ryzen1 (unshared)> ls
      conformance  c_rehash  go_default_test  openssl
      ryzen1 (unshared)> file conformance 
      conformance: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, with debug_info, not stripped
      
      
      

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

      quay.io/kubevirt/conformance:v1.0.0
      quay.io/kubevirt/conformance:v1.1.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. podman unshare 
      2. podman pull quay.io/kubevirt/conformance:v1.1.0
      2. cd $(podman image mount quay.io/kubevirt/conformance:v1.1.0)/usr/bin
      3. file conformance
      

      Actual results:

      conformance: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, with debug_info, not stripped
      
       

      Expected results:

      ryzen1 (unshared)> file conformance
      conformance: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, with debug_info, not stripped
       

      Additional info:

      It also appears that these images are not multi-arch manifest images.  Shouldn't they be by now?
      

              phoracek@redhat.com Petr Horacek
              jfrancin@redhat.com John Francini
              Anat Wax Anat Wax
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: