• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • CNV User Interface
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • CNV-13006 - [Platform Enablement] Support OpenShift Virtualization on AARCH64 (ARM)
    • ---
    • ---
    • None

      Description of problem:

      If following up to CNV-52176 brings us to architecture-agnostic temaplates that may miss the spec.template.architecture field because supporting multiple architecture (or use some other approach to expose the set of supported architectures), should the UI expose this field when the users instantiate a template to force scheduling on the proper architecture?
      
      Should the architecture field allow an empty string (i.e., scheduling on any supported architecture)?
      
      Should the architecture field (or set of supported architectures) be shown in the list of DataVolumes and Templates?
       
      

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

      
      

      How reproducible:

      
      

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      
      

      Expected results:

      
      

      Additional info:

      
      

              mschatzm@redhat.com Matan Schatzman
              rhn-support-adistefa Alessandro Di Stefano
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: