maas-dhcp-helper stopped working which gives issues with DNS updates
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Committed
|
Medium
|
Alexsander de Souza | ||
| 3.3 |
Fix Committed
|
Medium
|
Alexsander de Souza | ||
| 3.4 |
Fix Released
|
Medium
|
Alexsander de Souza | ||
Bug Description
We are using snap version/build 3.3.3-13184-
We have trouble with DNS records in MAAS getting stuck to the initial IP that the machine gets during enlistment. After enlistment we configure the other network interfaces (bond with vlans on top) of the machine to use a network for our OAM traffic which is separate from the PXE network used during enlistment and deployment. The machine does not have an IP address configured in the PXE network after deployment. Only a static IP in the OAM network (plus some other non-routed vlans when needed) is configure on the machine. This worked great with MAAS 3.2.7 but broke after upgrading to version 3.3.0 and 3.3.3.
In MAAS version 3.2.7 the temporary FQDN for the machine would be cleared after enlistment such that it's available for use when configuring the other network interfaces on the machine.
With this configuration we get an A record in DNS from the machine name to the IP it is assigned in the OAM network.
hostname.
In version 3.3.0 this is no longer the case, instead wet get two A records in DNS. One from the machine name to the IP in the PXE network which is not active and an interface dependent name to the IP in the OAM network.
hostname.
interface-
We have traced it to be maas-dhcp-helper not working anymore such that the DNS record created during enlistment is never removed.
Running maas-dhcp-helper after enlistment removes the DNS record in MAAS version 3.2.7 but not in 3.3.0 beta3 and later.
/snap/maas/
In MAAS version 3.3.0 beta3 updates for DHCP leases was changed from single update to bulk in commit ffa1fd3c4fe2a32
https:/
Steps to reproduce:
1. PXE boot a machine.
2. Check DNS in web interface that a DNS record exist for the machine.
3. Run maas-dhcp-helper to remove the lease.
4. Check DNS in web interface to see if DNS record was removed or not.
Related branches
- Alexsander de Souza: Approve
- MAAS Lander: Approve
-
Diff: 122 lines (+45/-6)4 files modifiedsrc/maasserver/rpc/leases.py (+27/-0)
src/maasserver/rpc/tests/test_leases.py (+13/-3)
src/maastesting/factory.py (+4/-2)
src/provisioningserver/rackdservices/lease_socket_service.py (+1/-1)
- Alberto Donato: Approve
- MAAS Lander: Approve
-
Diff: 85 lines (+16/-5)4 files modifiedsrc/maasserver/rpc/leases.py (+2/-0)
src/maasserver/rpc/tests/test_leases.py (+9/-2)
src/maastesting/factory.py (+4/-2)
src/provisioningserver/rackdservices/lease_socket_service.py (+1/-1)
- Alberto Donato: Approve
- MAAS Lander: Approve
-
Diff: 85 lines (+16/-5)4 files modifiedsrc/maasserver/rpc/leases.py (+2/-0)
src/maasserver/rpc/tests/test_leases.py (+9/-2)
src/maastesting/factory.py (+4/-2)
src/provisioningserver/rackdservices/lease_socket_service.py (+1/-1)
| Alberto Donato (ack) wrote | #1 |
| Bernard Stafford (bernard010) wrote | #2 |
| Christian Grabowski (cgrabowski) wrote | #3 |
| Changed in maas: | |
| status: | New → Incomplete |
| Tom-Erik Røberg (tom-erik-roberg) wrote | #4 |
| Changed in maas: | |
| status: | Incomplete → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Alexsander de Souza (alexsander-souza) |
| milestone: | none → 3.5.0 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Matus Kosut (matuskosut) wrote | #5 |
This might be related to LP:2025159