• Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • 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:

      
      

        1. architecture1.png
          architecture1.png
          248 kB
        2. architecture2.png
          architecture2.png
          245 kB
        3. template_on_arm.png
          template_on_arm.png
          270 kB
        4. architecture3.png
          architecture3.png
          214 kB

              upalatuc@redhat.com Ugo Palatucci
              rhn-support-adistefa Alessandro Di Stefano
              Leon Kladnitsky Leon Kladnitsky
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: