-
Bug
-
Resolution: Done
-
Critical
-
4.15, 4.16.0
-
None
-
False
-
-
Fixes HyperShift ability to generate ignition for 4.14 nodepools by matching the versions of RHEL openssl libraries used by HyperShift Control Plane Operator and the MachineConfig Operator tools that it uses.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-36863. The following is the description of the original issue:
—
Description of problem:
HCP deployment fails with error:
Hardware:
> Disk encryption requirements: Missing ignition information.
It is observed that installation is stuck as ignition is not available.
When checked the ignition server logs observed the below error message.
~~~ 2024-07-04T13:27:53.272449113Z {"level":"info","ts":"2024-07-04T13:27:53Z","logger":"get-payload","msg":"machine-config-operator process completed","time":"0s","output":"FIPS mode is enabled, but the required OpenSSL backend is unavailable\n"}
2024-07-04T13:27:53.291079347Z {"level":"error","ts":"2024-07-04T13:27:53Z","msg":"Reconciler error","controller":"secret","controllerGroup":"","controllerKind":"Secret","Secret":{"name":"token-nodepool-example-1-2efdaff7","namespace":"example-example"},"namespace":"example-example","name":"token-nodepool-example-1-2efdaff7","reconcileID":"4b82d54e-5a0b-4551-95e0-800dffb6bc26","error":"error getting ignition payload: failed to execute machine-config-operator: machine-config-operator process failed: exit status 1
~~~
Version-Release number of selected component (if applicable):
How reproducible:
100 %
Steps to Reproduce:
1. Deploy HCP cluster from ACM
2. Check the node status
3. Check the ignition server pod logs
Actual results:
installation get stuck
Expected results:
installation should be completed
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
