Actions
Bug #26525
closediPXE embedded PXE loader is causing DHCP conflict
Description
This is because during DHCP conflict check, PXE loader URL is different due to token:
2019-04-03T12:38:57 [I|app|4ada5e10] Started GET "/unattended/built?token=4e5ae70c-2ae1-40d3-952e-6b34eea9b17d" for 192.168.200.10 at 2019-04-03 12:38:57 +0100 2019-04-03T12:38:57 [I|app|4ada5e10] Processing by UnattendedController#built as TEXT 2019-04-03T12:38:57 [I|app|4ada5e10] Parameters: {"token"=>"4e5ae70c-2ae1-40d3-952e-6b34eea9b17d"} 2019-04-03T12:38:57 [D|app|4ada5e10] Current user set to foreman_api_admin (admin) 2019-04-03T12:38:57 [D|app|4ada5e10] Found lena-flickner.foreman.local.com 2019-04-03T12:38:57 [I|app|4ada5e10] unattended: lena-flickner.foreman.local.com is built! 2019-04-03T12:38:57 [D|app|4ada5e10] Comparing ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE"] == ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE?token=4e5ae70c-2ae1-40d3-952e-6b34eea9b17d"] 2019-04-03T12:38:57 [D|app|4ada5e10] Comparing ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE"] == ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE?token=4e5ae70c-2ae1-40d3-952e-6b34eea9b17d"] 2019-04-03T12:38:57 [D|app|4ada5e10] Comparing ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE"] == ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE?token=4e5ae70c-2ae1-40d3-952e-6b34eea9b17d"] 2019-04-03T12:38:57 [D|app|4ada5e10] Comparing ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE"] == ["52:54:00:f9:ca:60", "192.168.200.88", "192.168.200.0", "http://192.168.200.10:3000/unattended/iPXE?token=4e5ae70c-2ae1-40d3-952e-6b34eea9b17d"] 2019-04-03T12:38:57 [W|app|4ada5e10] DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists 2019-04-03T12:38:57 [W|app|4ada5e10] Not queueing Nic::Managed: ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] and ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] 2019-04-03T12:38:57 [W|app|4ada5e10] Not queueing Nic::Managed: ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] and ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] 2019-04-03T12:38:57 [D|app|4ada5e10] Current organization set to Raptor 2019-04-03T12:38:57 [D|app|4ada5e10] Current location set to Regus office 2019-04-03T12:38:57 [D|app|4ada5e10] Current location set to none 2019-04-03T12:38:57 [D|app|4ada5e10] Current organization set to none 2019-04-03T12:38:57 [W|app|4ada5e10] Not queueing Nic::Managed: ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] and ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] 2019-04-03T12:38:57 [W|app|4ada5e10] Not queueing Discovery reboot: Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists 2019-04-03T12:38:57 [W|app|4ada5e10] Failed to set Build on lena-flickner.foreman.local.com: ["Conflict DHCP records lena-flickner.foreman.local.com-52:54:00:f9:ca:60/192.168.200.88 already exists"] 2019-04-03T12:38:57 [I|app|4ada5e10] Completed 409 Conflict in 308ms (ActiveRecord: 38.8ms)
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6645 added
Updated by Lukas Zapletal almost 5 years ago
- Related to Bug #27877: DHCP conflict when editing PXE loader for existing host added
Updated by Lukas Zapletal almost 5 years ago
- Status changed from Ready For Testing to Rejected
The filename option should not be subject of conflict checks, going to solve this in the related issue.
Actions