[2.5] MAAS rack is not writing dhcpd.conf hostmap for deploying machine
Bug #1785078 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
A machine in deploying state got the IP address from the dynamic range instead of getting the IP address from the static range (as it was auto-assigned).
MAAS auto-assigned the machine with '10.245.143.206' (see calm-poodle.png) but the machine got '10.245.136.26' and no hostmap (see dhcpd.conf) was written.
2: eno1: <BROADCAST,
link/ether 94:18:82:7a:72:44 brd ff:ff:ff:ff:ff:ff
inet 10.245.136.26/21 brd 10.245.143.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::9618:
valid_lft forever preferred_lft forever
Related branches
~blake-rouse/maas:rackd-timeout-dhcp-configure
Merged
into
maas:master
- Mike Pontillo (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 198 lines (+75/-6)4 files modifiedsrc/maasserver/dhcp.py (+14/-4)
src/maasserver/tests/test_dhcp.py (+3/-1)
src/provisioningserver/rpc/clusterservice.py (+32/-0)
src/provisioningserver/rpc/tests/test_clusterservice.py (+26/-1)
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
milestone: | 2.5.0alpha2 → 2.5.0beta1 |
status: | Fix Released → In Progress |
Changed in maas: | |
status: | In Progress → Won't Fix |
status: | Won't Fix → Fix Released |
Changed in maas: | |
milestone: | 2.5.0beta1 → 2.5.0alpha2 |
To post a comment you must log in.