XML

Word

Printable

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

Provide the user with detailed reports of any errors that occur during installation, with sufficient information to immediately detect and diagnose the problem - even if the error occurs prior to the step where cluster installation is started in the assisted-service.

Why is this important?

Many of the common failure modes occur early in the process, and are currently detectable only from a timeout. When the failure occurs, the reason is not presented to the user and this will generate support requests. In most cases the behaviour is similar to IPI baremetal, but we aspire to better usability in the agent-based installer.

Unable to pull container images to run services
Systemd services fail to start because of reasons (e.g. no host detects rendezvous IP)
Host-specific configurations are not successfully applied (i.e. apply-host-config service does not complete, and errors are present in /var/run/agent-installer/host-config-failures)
Insufficient agents are booted to begin the cluster installation (i.e. start-cluster-installation does not start the cluster installation).

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>

is related to

OCPBUGS-15747 Installer should report if not enough agents are booted