[OKD-SCOS v4.17] UPI install with agent installer fails for 4.17.0-0.okd-scos-2024-06-27-091238 #1964
Replies: 6 comments 3 replies
-
Thank you. We'll surface this. |
Beta Was this translation helpful? Give feedback.
-
Similar issue here - trying to install SNO with assisted Installer with config from this file: Here OKD version is older - 4.16 , but got same error - first I tried real pull secret generated at RH Hybrid Cloud Console , then dummy pull secret as in this case, none worked. I'm rather new to OKD installation, hoped that assisted installer could be easiest way ... |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Same failure with v4.17.0-0.okd-scos-2024-07-16-072426 that contains openshift/assisted-service#6552 that "seems" to address this problem |
Beta Was this translation helpful? Give feedback.
-
@titou10titou10 @izderadicka @flauschi1985 Thank you for bringing it up. The reason you see this behavior is because of the way assisted-service validates pull-secret - basically going over all images in @titou10titou10 Notice that the images specified in |
Beta Was this translation helpful? Give feedback.
-
I got it to go further !
Verify that the env variables are correct for the assisted-service pod:
|
Beta Was this translation helpful? Give feedback.
-
(this is in relation to discussion #1960)
Context
Trying to install a SNO (Single Node) cluster:
It is important to note that the install works perfectly well with the exact same agent and install config files for OKD-FCOS v4.15.0-0.okd-2024-03-10-010116
I also have tried for a multi-node cluster, it fails the same way
Summary
It fails with the following error:
Details
install-config.yaml:
agent-config.yaml
The install fails after a few minutes the node boots, but the process fails, looping forever
So the "agent-register-infraenv.service" fails to start because it needs a pull secret for "registry.ci.openshift.org"?
Adding the following in
assisted-service.env
file does not change anything. EitherAlso, it seems the service is not able to parse variables
EC_PUBLIC_KEY_PEM
(?) andEC_PRIVATE_KEY_PEM
(?) from its own generated (?)/usr/local/share/assisted-service/assisted-service.env
file?Removing
EC_PUBLIC_KEY_PEM
andEC_PRIVATE_KEY_PEM
values fromassisted-service.env
file maked the warning disappear but the install still failsOriginal content of the
/usr/local/share/assisted-service/assisted-service.env
file on the nodeBeta Was this translation helpful? Give feedback.
All reactions