XML

Word

Printable

Details

Type: Epic
Resolution: Done
Priority: Normal
Fix Version/s: openshift-4.11
Affects Version/s: None
Component/s: None
Labels:

Epic Name:
Perform installation validations
Blocked:
False
Ready:
False
Epic Status:
Done
Feature Link:
OCPPLAN-8150 - Agent-Based Installer GA
Flagged:

Impediment
Parent Link:
OCPPLAN-8150Agent-Based Installer GA
Hierarchy Progress:
100
Hierarchy Progress Bar:

100% 100%
Release Note Text:

Hide
The Agent-based Installer performs validations on:
*Installation image generation: The user-provided manifests are checked for validity and compatibility.
* Installation: The installation service checks the hardware available for installation and emits validation events that can be retrieved with the `openshift-install agent wait-for` subcommands. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#validations-before-agent-iso-creation_preparing-to-install-with-agent-based-installer[Installation validations].

Show
The Agent-based Installer performs validations on: *Installation image generation: The user-provided manifests are checked for validity and compatibility. * Installation: The installation service checks the hardware available for installation and emits validation events that can be retrieved with the `openshift-install agent wait-for` subcommands. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#validations-before-agent-iso-creation_preparing-to-install-with-agent-based-installer[Installation validations].
Release Note Type:
Feature
Release Note Status:
Done
Target Version:

openshift-4.11

SFDC Cases Links:
SFDC Cases Counter:

Description

Epic Goal

As an OpenShift infrastructure owner, I need the OpenShift installer to perform validations for disconnected, on-premises environments.

Why is this important?

Customers/Partners want to deploy OpenShift successfully and want to avoid installations failing if requirements are not met, and they want to find out as soon as a error condition (e.g. malformed inputs, missing requirement, insufficient hardware) is detected by the installer and be informed on what the error is and how to remediate or recover.

Scenarios

Acceptance Criteria

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

Dependencies (internal and external)

Previous Work (Optional):

https://github.com/openshift/assisted-service

Open questions::

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>

References

Bootable Ephemeral Installer Image for Disconnected Cluster 0 Deployments

Attachments

Issue Links

links to

openshift/openshift-docs#48673: [WIP]: Created a sub-dir for agent with a proposed TOC

openshift/openshift-docs#48673: Created a sub-dir for Agent-based Installer with a proposed TOC

Sub-Tasks

1.	Docs Tracker	Closed	Amrita Sakthivel (Inactive)
2.	QE Tracker	Closed	zhenying niu
3.	TE Tracker	Closed	Eric Rich
4.	PX Tracker	Closed	Eric Rich

Activity

People

Assignee:: pawan pinjarkar

Reporter:: Ju Lim

QA Contact:: zhenying niu

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2022/01/05 6:30 PM

Updated:: 2023/04/27 5:31 PM

Resolved:: 2022/08/03 8:23 PM