-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
-
When using the node-config ISO for installing a day2 node for the appliance flow, the agent-register-infraenv fails:
# journalctl -u agent-register-infraenv -l --no-pager May 29 11:58:01 localhost.localdomain podman[25317]: time="2024-05-29T11:58:01Z" level=info msg="Registering infraenv" May 29 11:58:01 localhost.localdomain agent-register-infraenv[25341]: time="2024-05-29T11:58:01Z" level=fatal msg="Failed to register infraenv with assisted-service: response status code does not match any response statuses defined for this endpoint in the swagger spec (status 422): {}"
After looking into the agent-gather, it seems that the problem is the large bundle (>64K) in 'addtitionalTrustBundle' property in infraenv.yaml. I.e. since the assisted-service is limiting the property size in the API (as the value is stored in DB using a string which is limited to 65,535 bytes).
The bundle is large as it's being populated directly from the 'openshift-config/user-ca-bundle' configmap on the cluster.
As a suggestion to resolve the issue, probably need to to understand why the user-ca-bundle is so large. Or, filter it before populating in the infraenv yaml to ensure its size is up to 64k.
Additional info:
Discussed on the following thread.
- duplicates
-
OCPBUGS-43990 Work around excess CA certs in additionalTrustBundle
- New