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

Re-Enable Current-Release non-upgrade Scenarios when 4.17 RPMs are Available

XMLWordPrintable

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

      None

      Show
      None
    • False
    • uShift Sprint 255

      Description of problem:

      USHIFT-3273 required scenarios dependent on 4.17 RPMs to be temporarily disabled because the packages are not yet present in the mirror repo.  Rather than deleting the tests, an arbitrary string was appended to the filenames of each scenario (`.pending-crel`). This prevents the scenarios from being copied to the scenario staging folder by the ci_phase_iso_boot.sh script.

       

      When 4.17 RPMs become available, remove `.pending.crel` from all scenarios and periodic scenarios. 

      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: