Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-3559

Eliminate installer-aro fork of installer

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • Unfork installer-aro
    • False
    • None
    • False
    • Green
    • In Progress
    • OCPSTRAT-1448 - Eliminate installer-aro fork of OpenShift Installer (Phase I)
    • OCPSTRAT-1448Eliminate installer-aro fork of OpenShift Installer (Phase I)
    • 6% To Do, 12% In Progress, 82% Done
    • Hide

      Nov 19

      Status: Green

      Figured out the permissions and infrastructure needed to run unit tests. John has a PR up for unit testing and he's working on removing the installer-aro fork from the wrapper. PR for creating ignition assets is finally ready for testing and there's progress in the generation of the ignition assets through unit tests. Should be green.

      Show
      Nov 19 Status: Green Figured out the permissions and infrastructure needed to run unit tests. John has a PR up for unit testing and he's working on removing the installer-aro fork from the wrapper. PR for creating ignition assets is finally ready for testing and there's progress in the generation of the ignition assets through unit tests. Should be green.
    • Installer Sprint 261

      Epic Goal

      • Eliminate the need to use the openshift/installer-aro fork of openshift/installer during the installation of an ARO cluster.

      Why is this important?

      • Maintaining the fork is time-consuming for the ARO and causes delays in rolling out new releases of OpenShift to ARO.

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. CORS-1888
      2. CORS-2743
      3. CORS-2744
      4. https://github.com/openshift/installer/pull/7600/files

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              zabitter Zane Bitter
              zabitter Zane Bitter
              Jinyun Ma
              Mike Gahagan Mike Gahagan
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: