-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.16, 4.17
-
None
In the agent installer, assisted-service must always use the openshift-baremetal-installer binary (which is dynamically linked) to ensure that if the target cluster is in FIPS mode the installer will be able to run. (This was implemented in MGMT-15150.)
A recent change for OCPBUGS-33227 has switched to using the statically-linked openshift-installer for 4.16 and later. This breaks FIPS on the agent-based installer.
It appears that CI tests for the agent installer (the compact-ipv4 job runs with FIPS enabled) did not detect this, because we are unable to correctly determine the "version" of OpenShift being installed when it is in fact a CI payload.
- blocks
-
OCPBUGS-34278 FIPS install not possible with agent-based installer
-
- Closed
-
- is caused by
-
OCPBUGS-33227 Latest OCP 4.16 Assisted Installer Failed to prepare the installation with: 'GLIBC_2.34' not found
-
- Closed
-
- is cloned by
-
OCPBUGS-34278 FIPS install not possible with agent-based installer
-
- Closed
-
- is related to
-
OCPBUGS-33999 OCP Cluster installation stuck, using Agent Based Installer
-
- Closed
-
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update
- mentioned on