New RPC for reporting foreign DHCP servers only accepts one server
Bug #1364097 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
At the moment, the RPC call ReportForeignDH
However, it makes more sense to pass *all* the IP addresses to the region and then let the region decide what to do with them. initially that can be "drop everything but the first one," but we may want to use the data in other ways later.
Related branches
lp:~gmb/maas/dhcp-rpc-2.0
- Gavin Panella (community): Approve
-
Diff: 231 lines (+72/-42)6 files modifiedsrc/maasserver/rpc/nodegroupinterface.py (+13/-2)
src/maasserver/rpc/regionservice.py (+2/-2)
src/maasserver/rpc/tests/test_regionservice.py (+44/-21)
src/provisioningserver/pserv_services/dhcp_probe_service.py (+7/-12)
src/provisioningserver/pserv_services/tests/test_dhcp_probe_service.py (+5/-4)
src/provisioningserver/rpc/region.py (+1/-1)
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
Revision history for this message
| Graham Binns (gmb) wrote Re: [Bug 1364097] Re: New RPC for reporting foreign DHCP servers only accepts one server | #2 |
| Changed in maas: | |
| status: | In Progress → Triaged |
| assignee: | Graham Binns (gmb) → nobody |
| Changed in maas: | |
| assignee: | nobody → Graham Binns (gmb) |
| Changed in maas: | |
| milestone: | 1.7.0 → next |
| Changed in maas: | |
| assignee: | Graham Binns (gmb) → nobody |
| Changed in maas: | |
| status: | Triaged → Won't Fix |
| milestone: | next → none |
To post a comment you must log in.
Given that the attached branch was rejected, did you land a separate fix for this?