BUG: single-node installation fails about okd

[gtomilko]

It seems like os-tree in fedora coreos 39.20240210.3.0 apply new ignition file after reboot which override my configuration

[codespearhead]

What document are you following for installing it?

[gtomilko]

@codespearhead https://docs.okd.io version 4.15 "Installing on a single node"

[gtomilko]

Full install log
install.log

[bshephar]

Is this the right IP address for your node?

Get "https://api-int.okd-virt.getty.edu:6443/api?timeout=32s": dial tcp 153.10.94.90:6443: connect: connection refused

It looks like the bootstrap process completed:

Bootstrap completed, server is going to reboot.
The system will reboot at Tue 2024-04-09 21:24:54 UTC!

So, I would expect that the node has rebooted from it's primary disk. You can ssh to it and check that the IP address is correct:

ip -o a

Check that it's listening on the API port:

sudo ss -tpnl | grep 6443

Here's mine for example:

❯ ssh [email protected] sudo ss -tpnl | grep 6443
LISTEN 0      4096                             *:6443             *:*    users:(("kube-apiserver",pid=1027626,fd=3))

[gtomilko]

Hi @bshephar ))

IP is correct but problem is it never finish install. It is still booting into DVD and try to install it again and again.

[titou10titou10]

How did you configure as boot device on your node? mine are boot on ssd then cdrom
So on first boot, it boots on cdrom as there is no OS on ssd, and then for the following reboots, it boots on ssd where the initial FCOS has been installed...

[gtomilko]

OK, now I'm on the next step ))) It boots into install media, goes though install to local disk and after reboot all configuration is lost. I added to bootstrap-in-place-for-live-iso.ign file all needed info for networking but it does not seems to be copied during install. Please advise ))

[codespearhead]

@codespearhead https://docs.okd.io version 4.15 "Installing on a single node"

I recommend trying the Assisted Installer to ensure there weren't any issues with the commands in the tutorial or their execution.

[mzukal]

Hi,
I am trying to install single node OKD using assisted installer using the approach described here: https://github.com/openshift/assisted-service/tree/master/deploy/podman#okd-configuration. Unfortunately, I am having trouble with the pull secret.
If I use {"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}} the installer does not let me continue with the following message:
pull secret for new cluster is invalid: pull secret must contain auth for "registry.ci.openshift.org"
I changed the pull secret to {"auths":{"registry.ci.openshift.org":{"auth":"aWQ6cGFzcwo="}}} which allows me to continue to set up the cluster and generate the discovery ISO. When I start the installation it ends in couple of minutes with the following message in the cluster event log:
Failed to prepare the installation due to an unexpected error: failed generating install config for cluster 19aeb098-0ad2-4566-967b-70a3dfc559d8: failed to get installer path: command 'oc adm release extract --command=openshift-baremetal-install --to=/data/install-config-generate/installercache/registry.ci.openshift.org/origin/release:4.16 --insecure=false registry.ci.openshift.org/origin/release:4.16 --registry-config=/tmp/registry-config2098566652' exited with non-zero exit code 1: error: unable to read image registry.ci.openshift.org/origin/release:4.16: Head "https://registry.ci.openshift.org/v2/origin/release/manifests/4.16": unauthorized: unable to validate token . Please retry later
What is the right pull secret to use for OKD? Is the podman approach still supported for OKD? Is there some up to date step by step guide how to install SNO OKD (this: https://hackmd.io/tDnHM2BoQru0VgqMGI_Q5g is probably outdated, right?).
Any help would be appreciated!

[codespearhead]

I suggest replying to the thread you created in #1196 , where your feedback on this very question is pending.

Hi, I am trying to install single node OKD using assisted installer using the approach described here: https://github.com/openshift/assisted-service/tree/master/deploy/podman#okd-configuration. Unfortunately, I am having trouble with the pull secret. If I use {"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}} the installer does not let me continue with the following message: pull secret for new cluster is invalid: pull secret must contain auth for "registry.ci.openshift.org" I changed the pull secret to {"auths":{"registry.ci.openshift.org":{"auth":"aWQ6cGFzcwo="}}} which allows me to continue to set up the cluster and generate the discovery ISO. When I start the installation it ends in couple of minutes with the following message in the cluster event log: Failed to prepare the installation due to an unexpected error: failed generating install config for cluster 19aeb098-0ad2-4566-967b-70a3dfc559d8: failed to get installer path: command 'oc adm release extract --command=openshift-baremetal-install --to=/data/install-config-generate/installercache/registry.ci.openshift.org/origin/release:4.16 --insecure=false registry.ci.openshift.org/origin/release:4.16 --registry-config=/tmp/registry-config2098566652' exited with non-zero exit code 1: error: unable to read image registry.ci.openshift.org/origin/release:4.16: Head "https://registry.ci.openshift.org/v2/origin/release/manifests/4.16": unauthorized: unable to validate token . Please retry later What is the right pull secret to use for OKD? Is the podman approach still supported for OKD? Is there some up to date step by step guide how to install SNO OKD (this: https://hackmd.io/tDnHM2BoQru0VgqMGI_Q5g is probably outdated, right?). Any help would be appreciated!

[mzukal]

Sorry for writing into multiple discussions but the information about the best approach to install SNO OKD seems contradicting to me. The suggested approach in #1196 is to use miniagent while the approach suggested in this discussion is to use assisted installer. The official documentation mentions only assisted installer but I was not able to install OKD with the latest version of the assisted installer.
Btw. I finally managed to reply to #1196, see #1196 (reply in thread).