bifrost-deploy: dnsmasq not giving boot file name

Bug #2028744 reported by Stefan Pinter
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kayobe
Fix Released
Undecided
Unassigned

Bug Description

**Bug Report**
hi! I try to build a multinode Openstack test environment with Kayobe. This is about the following: "Discovery of the overcloud is supported by the ironic inspector service running in the bifrost_deploy container on the seed. The service is configured to PXE boot unrecognised MAC addresses with an IPA ramdisk for introspection."

So my "to be provisioned/introspected" host is sending a DHCP DISCOVER and dnsmasq from inside the bifrost-deploy container is responding with a DHCPOFFER that does not contain a reference to a boot file. The container has some images in it though.

The pxe client tells me "no boot file name received"

what can I do? why are there only 3 issues on launchpad? are there some archived issues somewhere?

thank you very much for your time!

Kayobe Version: 2023.1

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

Looks like an error in configuration. Please provide more information.

Changed in kayobe:
status: New → Invalid
Revision history for this message
Stefan Pinter (nidrix-glandda) wrote :

i'd be very happy to provide my config. do you need the whole kayobe config? would it make sense that i push my whole config into a repo and link it here?

any hints on what variables i have to look at?

sadly the documentation of kayobe did not give me any hint.

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

a link to the repo with configuration would be great, especially if it is a clone of the kayobe-config repo.

Revision history for this message
Stefan Pinter (nidrix-glandda) wrote :

hello again! i pushed it there. it is a new repo though

https://github.com/stefanpinterBE/kayobe-config

description: updated
summary: - bifrost-deploy: dnsmasq not giving bootnfile name
+ bifrost-deploy: dnsmasq not giving boot file name
Revision history for this message
Michał Skibicki (grucha) wrote :

I've got this issue too. I can see that @mmalchuk repo is not available anymore so I posted my config on github https://github.com/skbki/kayobe-config-debug

I've run tcpdump while bare metal machine was booting.
https://pastebin.com/4EzT39Zg

Looks like dnsmasq in bifrost-deploy container isn't configured to serve any dhcp boot file.

Changed in kayobe:
status: Invalid → Confirmed
Revision history for this message
Daniel Martinez (entaltoaragon) wrote :

Hi,

Looks like dnsmasq.conf is not generated fine

Manually generating dnsmasq.conf following the template from: https://opendev.org/openstack/bifrost/src/branch/stable/2023.1/playbooks/roles/bifrost-ironic-install/templates/dnsmasq.conf.j2 seems to work

Cheers!

Revision history for this message
Maksim Malchuk (mmalchuk) wrote (last edit ):

Hi,

please provide the log of the 'seed service deploy' command with -vvvv option generated, configuration files from the $KOLLA_CONFIG_PATH and /etc/kolla/bifrost

Changed in kayobe:
status: Confirmed → Incomplete
Revision history for this message
Will Szumski (willjs) wrote :

My colleague Matt Anson spotted this: https://review.opendev.org/c/openstack/bifrost/+/902233. We have proposed a cherry-pick to 2023.1. That config section was made conditional in: https://github.com/openstack/bifrost/commit/8d273d13147bcdffdfa3e803ff46e15b18662b0b. This broke discovery.

Changed in kayobe:
status: Incomplete → Confirmed
Revision history for this message
Will Szumski (willjs) wrote :

Workaround is may be to set `dhcp_provider: none` in $KAYOBE_CONFIG_PATH/kolla/config/bifrost/bifrost.yml

Revision history for this message
Will Szumski (willjs) wrote :

This should now be in the latest kolla images. Let us know if you are still seeing this issue after trying the new images.

Changed in kayobe:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.