1.9rc3: Deploy Node failed to be deployed, because of the following error: DHCPv4 server is disabled.
Bug #1524091 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Unassigned | ||
| 1.9 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
In MAAS 1.9, if *only* an unmanaged network is configured (with external DHCP), the following error is seen when trying to deploy a node, or delete an already-deployed node:
Node failed to be deployed, because of the following error: DHCPv4 server is disabled.
We should only throw this error if the Node is attached to a subnet whose cluster interface is DHCP-managed.
Related branches
lp:~mpontillo/maas/fix-1524091-unmanaged-dhcp-for-deploy-and-delete-1.9
- Gavin Panella (community): Approve
-
Diff: 209 lines (+55/-29)2 files modifiedsrc/provisioningserver/rpc/dhcp.py (+30/-7)
src/provisioningserver/rpc/tests/test_dhcp.py (+25/-22)
lp:~mpontillo/maas/fix-1524091-unmanaged-dhcp-for-deploy-and-delete-trunk
- Gavin Panella (community): Approve
-
Diff: 207 lines (+54/-28)2 files modifiedsrc/provisioningserver/rpc/dhcp.py (+30/-7)
src/provisioningserver/rpc/tests/test_dhcp.py (+24/-21)
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| Changed in maas: | |
| milestone: | 1.9.0 → none |
To post a comment you must log in.
Tested the fix (in the linked branch) end-to-end with my local testbed. Seems to be working.