Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-6

Perform installation validations

XMLWordPrintable

    • Perform installation validations
    • False
    • False
    • Done
    • OCPPLAN-8150 - Agent-Based Installer GA
    • Impediment
    • OCPPLAN-8150Agent-Based Installer GA
    • 0% To Do, 0% In Progress, 100% Done
    • 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].
    • Feature
    • Done

      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

      1. ...

      Acceptance Criteria

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

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

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

      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>

      References

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

              ppinjark@redhat.com pawan pinjarkar
              julim Ju Lim
              zhenying niu zhenying niu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: