Actions
Bug #12986
closed
JW
VG
DHCP network boot filename can be incorrectly placed in DHCP Pool Options
Bug #12986:
DHCP network boot filename can be incorrectly placed in DHCP Pool Options
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
All
Description
After an upgrade from 2.5.2 to 2.6.0 we have been encountering an issue with network booting. Under inside the DHCP network configuration file, there is a configuration option that didn't exist before. That is preventing out networking booting from working properly
subnet 192.168.240.0 netmask 255.255.252.0 {
pool {
option domain-name-servers 192.168.243.254;
deny dynamic bootp clients;
failover peer "dhcp_lan";
filename "legacy.donotuse"; << it seems that this option is causing network booting to fail.
range 192.168.240.80 192.168.243.249;
}
option routers 192.168.243.254;
option domain-name-servers 192.168.243.254;
default-lease-time 14400;
ping-check true;
next-server 192.168.243.132;
if option arch = 00:06 {
filename "legacy.donotuse";
} else if option arch = 00:07 {
filename "/grubnetx64.efi";
} else if option arch = 00:09 {
filename "/grubnetx64.efi";
} else {
filename "legacy.donotuse";
}
The line in the pool configuration is overriding the if statements later in the configuration file.
I have tried to unset network booting, which will remove the line, but when I re-enable network booting it will add the line back in. I can't find an option where to update that filename.
VG Updated by Viktor Gurov over 4 years ago
- Assignee set to Viktor Gurov
- Target version set to 2.7.0
- Plus Target Version set to 22.05
VG Updated by Viktor Gurov over 4 years ago
- Status changed from New to Feedback
JP Updated by Jim Pingle over 4 years ago
- Subject changed from Default DHCP Pool Options to DHCP network boot filename can be incorrectly placed in DHCP Pool Options
Updating subject for release notes.
VG Updated by Viktor Gurov over 4 years ago
- % Done changed from 0 to 100
Applied in changeset commit:568fdc9f7f4d9d6952f6ef51c922dd3603c5aa30.
RL Updated by Reid Linnemann over 4 years ago
- Status changed from Feedback to Resolved
Actions