Hi Thomas, I don’t think it’s by design - it’s just missing from the default dnsmasq template - which you can easily extend by copying the default template to /etc/kolla/config/ironic/ironic-dnsmasq.conf and improving it. See [1]. We would also gladly accept patches and improve the default operator experience when deploying Ironic using Kolla-Ansible. [1]: https://opendev.org/openstack/kolla-ansible/src/commit/cf02acb1a5b370fd42550... Best regards, Michal
On 3 Nov 2025, at 15:08, Thomas Sell <thomas.sell@mdc-berlin.de> wrote:
Hey everyone,
I'm facing a weird issue when trying to enroll baremetal compute hosts into Ironic using the self-enrollment/discovery method. Our Openstack is running 2025.1 and is based on Kolla-Ansible/Kayobe.
What I'm seeing:
- New hosts iPXE boot into IPA ramdisk. - IPA does its thing, gathering information. - IPA tries to report back to http://{{ kolla_internal_fqdn }}:5050 - The API call fails because no nameservers are available.
I've tried to figure out where the IPA ramdisk is supposed to get its DNS config from and could not. There are no dhcp-options set in Ironic's dnsmasq.conf and looking at the Ansible template for this file, I believe this is by design. Inside the ramdisk /etc/resolv.conf is empty, yet IPA is configured to call-back to a FQDN, not an IP.
I'm a bit puzzled about how this is supposed to work. We're using IPA images downloaded from https://tarballs.openstack.org. Do I need to build my own image? I also cannot find any mention of a separate DNS config for Ironic introspection in the documentation.
Any help or hints are appreciated!
Best, Thomas