-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
5
-
False
-
-
False
-
-
-
Agent Sprint 273, Agent Sprint 274, Agent Sprint 275
User Story:
Run agent-tui on the nodes at the boot time. The agent-tui will be available through the mirrored release payload. For the nodes to invoke agent-tui at boot time, the agent-tui binary and associated libraries need to be present at /usr/local/bin https://github.com/openshift/installer/blob/25b5d2154bf53fac3d8e81f6f08e6630ae9d198b/data/data/agent/systemd/units/agent-interactive-console-serial%40.service#L13
Current implementation: agent-tui extraction happens at the build time of the ISO
Future implementation: agent-tui should be extracted at the boot time
Note: this should only happen in case of OVE and not generic appliance flow
-
-
- Implementation detail ***
-
Since the appliance registry is already available during the boot and containing the agent-installer-utils image, it could be probably easier to add a specific service to extract the agent TUI artifacts in the `unconfigured-ignition` command (when the interactive disconnected workflow is enabled), within the openshift-installer repo
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.
- is depended on by
-
AGENT-1184 OVE ISO build and release (TP - Ph1)
-
- In Progress
-
- links to