Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-3501

Split Upgrade Scenarios into a separate CI job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.17
    • None
    • None
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 255

      Description of problem:

      It was decided to split the upgrade scenarios to a separate periodic CI job to reduce the overhead of running too many VMs on a metal host.

      Make sure to update the blueprints to set the greenboot timeout configuration to 10m.

       

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

      How reproducible:

      100%

      Steps to Reproduce:

      n/a

      1. 
      2.
      3.
      

      Actual results:

      Scenarios that make use of current-release images based on 4.17 RPMs are not run.

      Expected results:

      The scenarios described in Actual Results should be runnable.

      Additional info:

      See github comment [0]https://github.com/openshift/microshift/pull/3353#issuecomment-2138434150 for context on why it was useful to just append a string to the filename of each scenario.

      [0]

              jcope@redhat.com Jon Cope
              jcope@redhat.com Jon Cope
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: