-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
OKD Agent Installer
-
False
-
-
False
-
Yellow
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
OKD users should be able to use the agent-based install method to install OKD FCOS clusters.
This should mostly work already, but there are some known differences between RHCOS and FCOS that we rely on (as evidenced by people trying to use the FCOS ISO by accident and it failing). Specifically, I vaguely recall that the semodule command used by the selinux.service may be missing from FCOS.
Ultimately we need CI testing of OKD. This may help alert us to upcoming issues in RHCOS before we encounter them in OCP.
- depends on
-
OKD-116 (partial) Switch over installer to SCOS boot image for baremetal
- Closed
-
OCPBUGS-25251 OKD: Agent-based Installer is broken on OKD/FCOS
- Closed
- is blocked by
-
OCPBUGS-24390 [OKD] Master-0 does not join the bootstrap control plane
- Closed
-
OCPBUGS-4038 OKD: skip enabling gatewayd.socket
- Closed
-
OCPBUGS-19299 OKD: Implement workaround to allow SNO installations for OKD/FCOS
- Closed
-
OCPBUGS-19300 OKD: Implement workaround to allow SNO installations for OKD/FCOS [release-4.14]
- Closed
-
OCPBUGS-19303 OKD: Agent-based Installer is broken on OKD/FCOS
- Closed
-
OCPBUGS-19307 OKD: Implement workaround to allow SNO installations for OKD/FCOS [release-4.13]
- Closed
-
OCPBUGS-19552 OKD: Agent-based Installer is broken for HA-deployments of OKD/FCOS when api-int.* endpoint is not defined
- Closed
-
OCPBUGS-26984 OKD: Agent-based Installer is broken on OKD/FCOS [4.14]
- Closed
-
OKD-90 Include okd-rpms in the payload, teach Assisted Installer to use it automatically
- Closed
- is related to
-
OCPBUGS-13955 Cannot override base image selection when creating agent ISO
- Closed
-
OCPBUGS-24479 Wrong UEFI entries created by the Assisted installer when the base OS is not RHCOS (OKD, OCP/SCOS)
- Closed
- relates to
-
AGENT-891 OKD SCOS Support
- Closed