Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect behavior since PR#1365 was merged #1381

Closed
gmarcy opened this issue Dec 24, 2023 · 0 comments
Closed

Incorrect behavior since PR#1365 was merged #1381

gmarcy opened this issue Dec 24, 2023 · 0 comments
Labels

Comments

@gmarcy
Copy link

gmarcy commented Dec 24, 2023

Describe the bug

Ever since PR#1365 was merged my systems all boot into the interactive menu instead of using the boot filename returned from DHCP server. images were built w/ explicit

bootloader_tftp_enabled: false

To Reproduce
Steps to reproduce the behavior:

  1. reboot a system using ipxe when dhcp returns a filename to use to boot. tftp-server is set to next-server here:
isset ${next-server} && isset ${proxydhcp/next-server} && goto choose-tftp || set tftp-server ${next-server} && goto load-custom-ipxe
  1. since filename is set you always end up in tftpmenu
:load-custom-ipxe
isset ${tftp-server} && isset ${filename} && goto tftpmenu
  1. tftpmenu never even uses filename, so will always end up here
chain --autofree tftp://${tftp-server}/menu.ipxe

Expected behavior

I expect it to use the filename I've configured dhcp to return and I expect it to use http on the server I've configured in the boot_domain rather then booting from the tftp server when I've disabled booting from tftp

Screenshots

Additional context

@gmarcy gmarcy added the bug label Dec 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant