Closed a-elie closed 3 months ago
Hi,
We are not working on FCOS builds of OKD any more. Please see these documents...
https://okd.io/blog/2024/06/01/okd-future-statement https://okd.io/blog/2024/07/30/okd-pre-release-testing
Please test with the OKD SCOS nightlies and file a new issue as needed.
Many thanks,
Jaime
Describe the bug
Agent service doesn't start on cluster nodes (booting from agent.iso) because okd-binaries.sh can't pull an okd image
Root cause : HTTPS_PROXY is not set and /etc/profile.d/proxy.sh doesn't exists
As a temp workaround, one can ssh to each node and add
export HTTP(S)_PROXY=_proxy_url_
beforepodman pull
line. After that, discovery and installation succeedsDon't know if it's related, but if I don't add HTTP(S)_PROXY in okd-configmap.yml, cluster nodes joins discovery without any problem (but installation fails because assisted-installer can't download installation files)
Version
Baremetal IPI (libvirt) with assisted installer agent (podman)
OS_IMAGES:
RELEASE_IMAGES:
How reproducible 100%
Log bundle