Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-68997 [Multiarch] spec.architecture doesn't auto-populate on ARM clusters despite kubernetes.io/arch=arm64
  3. CNV-69626

QE Verify: [Multiarch] spec.architecture doesn't auto-populate on ARM clusters despite kubernetes.io/arch=arm64

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • CNV User Interface
    • Quality / Stability / Reliability
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Description of problem:

      when setting up a VM with arm64 datasources ,
      
      configuration auto-populates  kubernetes.io/arch: arm64  when datasources are  arm based     spec:
            nodeSelector:
              kubernetes.io/arch: arm64 
      
      while spec.architecture has to be set explictly, ideally if nodeSelector is auto-populated with kubernetes.io/arch: arm64 , set spec.architecture to arm64 by default.

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

      4.20

      How reproducible:

      always

      Steps to Reproduce:

      1. To reproduce , open UI in a heterogeneous cluster. Make sure enable enableMultiArchBootImageImport in hco
      2. create a VM using fedora.arm64 datasource and create VM with instancetype flow from UI. Observe nodeselector is picked kubernetes.io/arch: arm64 
      3. on VM spec see, architectire is still amd64
      

      Actual results:

      spec.architecture is amd64 always  and must be set explicitly for non arm. This is too manual for big setups.

      Expected results:

      If nodeSelector is auto-populated with kubernetes.io/arch: arm64 , set spec.architecture to arm64 by default

      Additional info:

       

              rhn-support-lkladnit Leon Kladnitsky
              mschatzm@redhat.com Matan Schatzman
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: