XML

Word

Printable

Epic Name:
NoRegistryClusterInstall GA feature promotion
Activity Type:
Product / Portfolio Work
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Red
Epic Status:
In Progress
Feature Link:
OCPSTRAT-2251 - [GA] Agent Installer for OpenShift Virtualization - Day-1 and Day-2 add a new node w/o an external registry
Parent Link:
OCPSTRAT-2251[GA] Agent Installer for OpenShift Virtualization - Day-1 and Day-2 add a new node w/o an external registry
Hierarchy Progress Bar:

50% To Do, 13% In Progress, 38% Done
Status Summary:

Hide

10 Feb:

[Pawan] Started discussion with Andrea and Manoj about the test scenarios. Last week Pawan synced up MCO team and TRT team. Previously, it was decided that the extended tests will be written in the MCO repo. Created a draft PR https://github.com/openshift/machine-config-operator/pull/5620 However, it is not decided to write these tests into https://github.com/openshift/origin

Show
10 Feb: [Pawan] Started discussion with Andrea and Manoj about the test scenarios. Last week Pawan synced up MCO team and TRT team. Previously, it was decided that the extended tests will be written in the MCO repo. Created a draft PR https://github.com/openshift/machine-config-operator/pull/5620 However, it is not decided to write these tests into https://github.com/openshift/origin

Epic Goal

As described in https://github.com/openshift/enhancements/blob/master/dev-guide/feature-zero-to-hero.md we must prove that the NoRegistryClusterInstall feature:
works on ALL supported architectures, platforms, network types, and variants
must not regress any other part of OpenShift

Why is this important?

This is a required mandatory step to promote the NoRegistryClusterInstall feature as GA

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

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>

links to