| 2023-12-12 13:06:39 |
Jacopo Rota |
bug |
|
|
added bug |
| 2023-12-12 13:06:51 |
Jacopo Rota |
nominated for series |
|
maas/3.3 |
|
| 2023-12-12 13:06:51 |
Jacopo Rota |
bug task added |
|
maas/3.3 |
|
| 2023-12-12 13:06:51 |
Jacopo Rota |
nominated for series |
|
maas/3.4 |
|
| 2023-12-12 13:06:51 |
Jacopo Rota |
bug task added |
|
maas/3.4 |
|
| 2023-12-12 13:06:51 |
Jacopo Rota |
nominated for series |
|
maas/3.5 |
|
| 2023-12-12 13:06:51 |
Jacopo Rota |
bug task added |
|
maas/3.5 |
|
| 2023-12-12 13:06:56 |
Jacopo Rota |
maas/3.3: status |
New |
Triaged |
|
| 2023-12-12 13:06:58 |
Jacopo Rota |
maas/3.4: status |
New |
Triaged |
|
| 2023-12-12 13:07:07 |
Jacopo Rota |
maas/3.5: importance |
Critical |
High |
|
| 2023-12-12 13:07:09 |
Jacopo Rota |
maas/3.4: importance |
Undecided |
Critical |
|
| 2023-12-12 13:07:11 |
Jacopo Rota |
maas/3.3: importance |
Undecided |
Critical |
|
| 2023-12-12 13:09:15 |
Jacopo Rota |
description |
In different solqa runs (for example https://solutions.qa.canonical.com/testruns/fa952c11-c459-4eb2-82b6-e51b737dbef3), in a discourse post (https://discourse.maas.io/t/hosts-w-multiple-ips-have-multiple-a-records-created-v3-3-3/7651/8) and also on the reporter's homelab MAAS >= 3.3 is creating multiple A records for the name <machine>.<domain>. As a consequence, the dns resolution returns wrong data
```
dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60108
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f2c0be5af22ac4af0100000065785290f03797615562001b (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 192.168.1.222
ciscom4.maas. 30 IN A 172.0.2.11
```
(172.0.2.11 is the address on the boot interface, 192.168.1.222 is the address on the second interface).
The expected behaviour is that MAAS creates only one A record for the boot interface that resolves <machine>.<domain>.
For all the other interfaces, MAAS should create a dns record like <nic>.<machine>.<domain> that resolves to that interface's address.
In MAAS 3.2 the observed behaviour is correct:
```
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12068
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f229d1e1531ca4d301000000657858e8e491652723980002 (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 172.0.2.200
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:16 CET 2023
;; MSG SIZE rcvd: 85
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost enp1s0f1.ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost enp1s0f1.ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42539
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 103a5f56c262636601000000657858ebccee4b5cccda9899 (good)
;; QUESTION SECTION:
;enp1s0f1.ciscom4.maas. IN A
;; ANSWER SECTION:
enp1s0f1.ciscom4.maas. 30 IN A 192.168.1.31
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:19 CET 2023
;; MSG SIZE rcvd: 94
``` |
In different solqa runs (for example https://solutions.qa.canonical.com/testruns/fa952c11-c459-4eb2-82b6-e51b737dbef3), in a discourse post (https://discourse.maas.io/t/hosts-w-multiple-ips-have-multiple-a-records-created-v3-3-3/7651/8) and also on the reporter's homelab MAAS >= 3.3 is creating multiple A records for the name <machine>.<domain>. As a consequence, the dns resolution returns wrong data
```
dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60108
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f2c0be5af22ac4af0100000065785290f03797615562001b (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 192.168.1.222
ciscom4.maas. 30 IN A 172.0.2.11
```
(172.0.2.11 is the address on the boot interface, 192.168.1.222 is the address on the second interface).
The expected behaviour is that MAAS creates only one A record for the boot interface that resolves <machine>.<domain>.
For all the other interfaces, MAAS should create a dns record like <nic>.<machine>.<domain> that resolves to that interface's address.
In MAAS 3.2 the observed behaviour is correct:
```
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12068
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f229d1e1531ca4d301000000657858e8e491652723980002 (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 172.0.2.11
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:16 CET 2023
;; MSG SIZE rcvd: 85
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost enp1s0f1.ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost enp1s0f1.ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42539
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 103a5f56c262636601000000657858ebccee4b5cccda9899 (good)
;; QUESTION SECTION:
;enp1s0f1.ciscom4.maas. IN A
;; ANSWER SECTION:
enp1s0f1.ciscom4.maas. 30 IN A 192.168.1.222
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:19 CET 2023
;; MSG SIZE rcvd: 94
``` |
|
| 2023-12-12 13:16:23 |
Jacopo Rota |
description |
In different solqa runs (for example https://solutions.qa.canonical.com/testruns/fa952c11-c459-4eb2-82b6-e51b737dbef3), in a discourse post (https://discourse.maas.io/t/hosts-w-multiple-ips-have-multiple-a-records-created-v3-3-3/7651/8) and also on the reporter's homelab MAAS >= 3.3 is creating multiple A records for the name <machine>.<domain>. As a consequence, the dns resolution returns wrong data
```
dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60108
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f2c0be5af22ac4af0100000065785290f03797615562001b (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 192.168.1.222
ciscom4.maas. 30 IN A 172.0.2.11
```
(172.0.2.11 is the address on the boot interface, 192.168.1.222 is the address on the second interface).
The expected behaviour is that MAAS creates only one A record for the boot interface that resolves <machine>.<domain>.
For all the other interfaces, MAAS should create a dns record like <nic>.<machine>.<domain> that resolves to that interface's address.
In MAAS 3.2 the observed behaviour is correct:
```
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12068
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f229d1e1531ca4d301000000657858e8e491652723980002 (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 172.0.2.11
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:16 CET 2023
;; MSG SIZE rcvd: 85
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost enp1s0f1.ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost enp1s0f1.ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42539
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 103a5f56c262636601000000657858ebccee4b5cccda9899 (good)
;; QUESTION SECTION:
;enp1s0f1.ciscom4.maas. IN A
;; ANSWER SECTION:
enp1s0f1.ciscom4.maas. 30 IN A 192.168.1.222
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:19 CET 2023
;; MSG SIZE rcvd: 94
``` |
In different solqa runs (for example https://solutions.qa.canonical.com/testruns/fa952c11-c459-4eb2-82b6-e51b737dbef3), in a discourse post (https://discourse.maas.io/t/hosts-w-multiple-ips-have-multiple-a-records-created-v3-3-3/7651/8) and also on the reporter's homelab MAAS >= 3.3 is creating multiple A records for the name <machine>.<domain>. As a consequence, the dns resolution returns wrong data
```
dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60108
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f2c0be5af22ac4af0100000065785290f03797615562001b (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 192.168.1.222
ciscom4.maas. 30 IN A 172.0.2.11
```
(172.0.2.11 is the address on the boot interface, 192.168.1.222 is the address on the second interface).
The expected behaviour is that MAAS creates only one A record for the boot interface that resolves <machine>.<domain>.
For all the other interfaces, MAAS should create a dns record like <nic>.<machine>.<domain> that resolves to that interface's address.
In MAAS 3.2 the observed behaviour is correct:
```
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12068
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f229d1e1531ca4d301000000657858e8e491652723980002 (good)
;; QUESTION SECTION:
;ciscom4.maas. IN A
;; ANSWER SECTION:
ciscom4.maas. 30 IN A 172.0.2.11
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:16 CET 2023
;; MSG SIZE rcvd: 85
r00ta@r00ta-ThinkPad-T420:~/repos/maas-matrix-tests$ dig @localhost enp1s0f1.ciscom4.maas
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> @localhost enp1s0f1.ciscom4.maas
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42539
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 103a5f56c262636601000000657858ebccee4b5cccda9899 (good)
;; QUESTION SECTION:
;enp1s0f1.ciscom4.maas. IN A
;; ANSWER SECTION:
enp1s0f1.ciscom4.maas. 30 IN A 192.168.1.222
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Tue Dec 12 13:58:19 CET 2023
;; MSG SIZE rcvd: 94
```
### STEPS TO REPRODUCE
1) install maas
2) commission a VM or a server with 2 interfaces
3) Once the machine is commissioned, assign a static IP to the non-boot interface
4) try to resolve <machine>.<domain> with dig |
|
| 2023-12-13 19:30:15 |
Jeffrey Chang |
bug |
|
|
added subscriber Jeffrey Chang |
| 2023-12-14 09:25:57 |
Jacopo Rota |
maas/3.3: assignee |
|
Jacopo Rota (r00ta) |
|
| 2023-12-14 09:25:59 |
Jacopo Rota |
maas/3.4: assignee |
|
Jacopo Rota (r00ta) |
|
| 2023-12-14 09:26:00 |
Jacopo Rota |
maas/3.5: assignee |
|
Jacopo Rota (r00ta) |
|
| 2023-12-14 09:26:04 |
Jacopo Rota |
maas/3.5: milestone |
|
3.5.0 |
|
| 2023-12-14 09:26:06 |
Jacopo Rota |
maas/3.4: milestone |
|
3.4.x |
|
| 2023-12-14 09:26:09 |
Jacopo Rota |
maas/3.3: milestone |
|
3.3.x |
|
| 2023-12-15 07:18:41 |
Jacopo Rota |
maas/3.5: importance |
High |
Critical |
|
| 2023-12-15 07:18:43 |
Jacopo Rota |
maas/3.5: importance |
Critical |
High |
|
| 2023-12-15 10:18:48 |
Jacopo Rota |
merge proposal linked |
|
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/457612 |
|
| 2023-12-15 10:18:53 |
Jacopo Rota |
maas/3.5: status |
Triaged |
In Progress |
|
| 2023-12-15 20:43:52 |
MAAS Lander |
maas/3.5: status |
In Progress |
Fix Committed |
|
| 2024-01-02 07:22:45 |
Jacopo Rota |
merge proposal linked |
|
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/457803 |
|
| 2024-01-02 07:22:51 |
Jacopo Rota |
merge proposal linked |
|
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/457804 |
|
| 2024-01-02 07:22:57 |
Jacopo Rota |
merge proposal linked |
|
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/457806 |
|
| 2024-01-02 07:23:06 |
Jacopo Rota |
maas/3.4: status |
Triaged |
In Progress |
|
| 2024-01-02 07:23:08 |
Jacopo Rota |
maas/3.3: status |
Triaged |
In Progress |
|
| 2024-01-02 08:55:17 |
MAAS Lander |
maas/3.3: status |
In Progress |
Fix Committed |
|
| 2024-01-02 09:38:31 |
MAAS Lander |
maas/3.4: status |
In Progress |
Fix Committed |
|
| 2024-01-04 09:10:21 |
Adam Collard |
maas/3.4: milestone |
3.4.x |
3.4.0 |
|
| 2024-01-05 09:47:37 |
Alberto Donato |
maas/3.4: status |
Fix Committed |
Fix Released |
|
| 2024-01-17 22:29:09 |
Alexsander de Souza |
maas/3.3: milestone |
3.3.x |
3.3.5 |
|
| 2024-01-17 22:31:36 |
Alexsander de Souza |
maas/3.3: status |
Fix Committed |
Fix Released |
|
| 2024-03-05 12:20:27 |
Anton Troyanov |
maas: milestone |
3.5.0 |
3.5.0-beta1 |
|
| 2024-03-05 12:25:17 |
Anton Troyanov |
maas: status |
Fix Committed |
Fix Released |
|
