-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
n/a
-
None
- What is the nature and description of the request?
- Customer experience using preview installer (2.6 containerized bundle)
- Installer completed with failures, but customer didn't recognize impact as the installer continued running and successfully completed some components. The AAP UI stood up successfully and failed state was apparent based on inability to sync projects. The root cause was determined to be insufficient disk space which led the the Controller post-install steps being skipped.
- Installer did report failures, impact from customer's perspective was not clear.
- Why does the customer need this? (List the business requirements here)
- Some steps in the installer can fail and retry (or be ignored), so the customer was conditioned to seeing some acceptable red. In this case, the error impacted the state of the platform in an unexpected way.
- How would you like to achieve this? (List the functional requirements here)
- Surface errors that prevent important sections of the installer from running (e.g. post-install) and the end of the run.
- Provide remediation steps for an installation that completes in a partially successful state to support manual fix. In this case, the failed state was apparent because control plane EEs were not properly configured, preventing the customer from syncing projects. With RH help, the customer was able to manually set up configuration files and run appropriate awx commands to complete configuration.
- List any affected known dependencies: Doc, UI etc..
- Installer, Docs
Please note, this was experienced during a preview installation of AAP 2.6.