The value of 'next-server' in the dhcp config is wrong.
Bug #1081692 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Julian Edwards | ||
| 1.2 |
Fix Released
|
Critical
|
Julian Edwards | ||
| maas (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
If the cluster is not on the same machine as the region controller, the value of the 'next-server' address is wrong: it is the address of the region controller.
The default (i.e. when the 'next-server' directive is not present) is to use the address of the server which has given the IP address to pxe boot. This is exactly what we want here: the pserv is always on the same machine as the dhcp server. So I suggest we get rid of that line in the dhcp config.
Related branches
lp:~julian-edwards/maas/next-server-wrong-bug-1081692
- Raphaël Badin (community): Approve
-
Diff: 97 lines (+2/-13)4 files modifieddocs/configure.rst (+1/-3)
src/provisioningserver/dhcp/config.py (+0/-2)
src/provisioningserver/dhcp/tests/test_writer.py (+1/-5)
src/provisioningserver/dhcp/writer.py (+0/-3)
lp:~julian-edwards/maas/1.2-next-server-wrong-bug-1081692
- Raphaël Badin (community): Approve
-
Diff: 96 lines (+2/-12)4 files modifieddocs/configure.rst (+1/-2)
src/provisioningserver/dhcp/config.py (+0/-2)
src/provisioningserver/dhcp/tests/test_writer.py (+1/-5)
src/provisioningserver/dhcp/writer.py (+0/-3)
| Changed in maas: | |
| milestone: | none → 12.10-stabilization |
| no longer affects: | maas/12.04-nocobbler |
| Changed in maas (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in maas (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
