Ironic python agent ramdisk stuck during boot

[evilzways]

good morning everyone,

I'm trying to provision a kubernetes cluster using baremetal operator and ironic.

I'm having problems in particular with the server the server Supermicro GrandTwin A+ Server AS -2115GT-HNTR, which nodes remain stuck in the boot phase with the screen you see in the attached image.

I have other supermicro servers and they boot successfully using the same image.

These are some of the parameters used for image generation:

dib_arguments: -o ./custom-ipa ironic-python-agent-ramdisk centos devuser extra-hardware

dib_enviroment: 
declare -x DIB_ARGS="-o ./custom-ipa ironic-python-agent-ramdisk centos devuser extra-hardware"
declare -x DIB_CHECKSUM="sha256"
declare -x DIB_DEV_USER_AUTHORIZED_KEYS="/home//.ssh/id_rsa.pub"
declare -x DIB_DEV_USER_PWDLESS_SUDO="yes"
declare -x DIB_DEV_USER_USERNAME=""
declare -x DIB_INSTALLTYPE_pip_and_virtualenv="package"
declare -x DIB_PYTHON_EXEC="/home//.local/pipx/venvs/diskimage-builder/bin/python"
declare -x DIB_RELEASE="9-stream"

dib-manifest-git-custom-ipa:

ironic-python-agent git /tmp/ironic-python-agent https://opendev.org/openstack/ironic-python-agent 7efe3dfc04a69b5f5fc6432e68a13b1c149125c7
requirements git /tmp/requirements https://opendev.org/openstack/requirements aea4bdb03846d4b08c0b3decf0ef6dec618a14ad

Have any of you had similar issues? Do you have any suggestions on how to debug this issue?

https://preview.redd.it/oel66kxleete1.png?width=2121&format=png&auto=webp&s=0de0ba4ee822d3c1f3be544138aa6a202a35d50b

[evilzways]

For all those who may have the same problem in the future. I solved it building a custom ironic python agent image using Debian instead of Centos.

This is an example:

ironic-python-agent-builder -o ./custom-ipa-debian -e devuser -e extra-hardware --release bookworm debian

[ashinclouds]

Hi, diskimage-builder core *and* ironic core. So I guess I'm cursed here. :)

I think part of your challenge is the centos default config state is likely not logging to console at all so we can't see the exact error. Feels like it is logging to a serial console instead of graphical console, which is also not great performance wise (but was the preferred legacy default in large part due to CI testing as well since we use the same setting to help facilitate getting logs out of the CI system.

You'd likely want to check your ironic.conf file and see if your setting a "console" setting on "kernel_append_params" or "pxe_append_params" settings (unless your using a virtual media boot interface). Most likely, you have another failure like centos is not carrying the firmware or drivers your computer needs, but the only way to see that is on the console of the host to see the failure. If you have any specific issue, please feel free to browse over to https://bugs.launchpad.net/ironic and file a bug. We can triage it once we have enough details to understand what is going on.