[2.0] Can't start OMAPI protocol: address not available
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
LaMont Jones | ||
Bug Description
After working around 1564925, maas-dhcp6 tells me (repeatedly):
Apr 1 05:36:10 kohlrabi dhcpd[23854]: Bound to *:547
Apr 1 05:36:10 kohlrabi sh[23854]: Bound to *:547
Apr 1 05:36:10 kohlrabi sh[23854]: Listening on Socket/
Apr 1 05:36:10 kohlrabi sh[23854]: Sending on Socket/
Apr 1 05:36:10 kohlrabi dhcpd[23854]: Listening on Socket/
Apr 1 05:36:10 kohlrabi sh[23854]: Can't start OMAPI protocol: address not available
Apr 1 05:36:10 kohlrabi dhcpd[23854]: Sending on Socket/
Apr 1 05:36:10 kohlrabi dhcpd[23854]: Can't start OMAPI protocol: address not available
Apr 1 05:36:10 kohlrabi dhcpd[23854]: Server starting service.
Apr 1 05:36:15 kohlrabi dhcpd[23854]: Can't start OMAPI protocol: address not available
Apr 1 05:36:35 kohlrabi dhcpd[23854]: message repeated 4 times: [ Can't start OMAPI protocol: address not available]
...
I suspect that this is because maas-dhcp already is already listening on the socket.
Related branches
- Blake Rouse (community): Approve
-
Diff: 520 lines (+116/-49)9 files modifiedsrc/maasserver/dhcp.py (+2/-2)
src/maastesting/factory.py (+12/-2)
src/provisioningserver/dhcp/__init__.py (+3/-0)
src/provisioningserver/dhcp/omshell.py (+10/-1)
src/provisioningserver/dhcp/tests/test_omshell.py (+72/-40)
src/provisioningserver/rpc/dhcp.py (+3/-1)
src/provisioningserver/rpc/tests/test_dhcp.py (+7/-2)
src/provisioningserver/templates/dhcp/dhcpd.conf.template (+2/-0)
src/provisioningserver/templates/dhcp/dhcpd6.conf.template (+5/-1)
| Changed in maas: | |
| milestone: | none → 2.0.0 |
| Changed in maas: | |
| assignee: | nobody → LaMont Jones (lamont) |
| Changed in maas: | |
| importance: | Undecided → Critical |
| status: | New → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
