| 2018-10-12 20:57:25 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2018-10-12 20:57:30 |
Andres Rodriguez |
maas: milestone |
|
2.5.0rc1 |
|
| 2018-10-12 20:57:32 |
Andres Rodriguez |
maas: importance |
Undecided |
Medium |
|
| 2018-10-12 20:57:35 |
Andres Rodriguez |
maas: importance |
Medium |
Critical |
|
| 2018-10-12 20:57:37 |
Andres Rodriguez |
maas: status |
New |
Triaged |
|
| 2018-10-12 20:58:59 |
Andres Rodriguez |
attachment added |
|
region-controller-ips.png https://bugs.launchpad.net/maas/+bug/1797632/+attachment/5200515/+files/region-controller-ips.png |
|
| 2018-10-12 20:59:08 |
Andres Rodriguez |
attachment added |
|
observed-ip-address.png https://bugs.launchpad.net/maas/+bug/1797632/+attachment/5200516/+files/observed-ip-address.png |
|
| 2018-10-12 21:12:35 |
Andres Rodriguez |
description |
MAAS is running in a VM with two interfaces. One of which doesn't have any ip addresses:
root@autopkgtest:/etc/bind/maas# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether de:ad:be:ef:6b:b3 brd ff:ff:ff:ff:ff:ff
inet 10.245.136.6/21 brd 10.245.143.255 scope global ens4
valid_lft forever preferred_lft forever
inet6 fe80::dcad:beff:feef:6bb3/64 scope link
valid_lft forever preferred_lft forever
However, one IP is added for the internal domain that doesn't exist:
root@autopkgtest:/etc/bind/maas# cat zone.maas-internal
; Zone file modified: 2018-10-12 20:44:32.390833.
$TTL 15
@ IN SOA maas-internal. nobody.example.com. (
0000000127 ; serial
600 ; Refresh
1800 ; Retry
604800 ; Expire
15 ; NXTTL
)
@ 15 IN NS maas.
10-245-136-0--21 15 IN A 10.245.136.18
10-245-136-0--21 15 IN A 10.245.136.6
If we look at the db shell, we see:
autopkgtest | 1 | ens3 | physical | 52:54:00:12:34:56 | 10.245.136.18 | DISCOVERED | 10.245.136.0/21 | 0 | fabric-0
autopkgtest | 2 | ens4 | physical | de:ad:be:ef:6b:b3 | 10.245.136.6 | STICKY | 10.245.136.0/21 | 0 | fabric-0 |
MAAS is running in a VM with two interfaces. One of which doesn't have any ip addresses:
root@autopkgtest:/etc/bind/maas# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether de:ad:be:ef:6b:b3 brd ff:ff:ff:ff:ff:ff
inet 10.245.136.6/21 brd 10.245.143.255 scope global ens4
valid_lft forever preferred_lft forever
inet6 fe80::dcad:beff:feef:6bb3/64 scope link
valid_lft forever preferred_lft forever
However, one IP is added for the internal domain that doesn't exist:
root@autopkgtest:/etc/bind/maas# cat zone.maas-internal
; Zone file modified: 2018-10-12 20:44:32.390833.
$TTL 15
@ IN SOA maas-internal. nobody.example.com. (
0000000127 ; serial
600 ; Refresh
1800 ; Retry
604800 ; Expire
15 ; NXTTL
)
@ 15 IN NS maas.
10-245-136-0--21 15 IN A 10.245.136.18
10-245-136-0--21 15 IN A 10.245.136.6
If we look at the db shell, we see:
autopkgtest | 1 | ens3 | physical | 52:54:00:12:34:56 | 10.245.136.18 | DISCOVERED | 10.245.136.0/21 | 0 | fabric-0
autopkgtest | 2 | ens4 | physical | de:ad:be:ef:6b:b3 | 10.245.136.6 | STICKY | 10.245.136.0/21 | 0 | fabric-0
********* A ver interesting thing, is that there's another machine in the subnet, with the same hostname that's actually causing the issue. |
|
| 2018-10-12 21:16:56 |
Andres Rodriguez |
description |
MAAS is running in a VM with two interfaces. One of which doesn't have any ip addresses:
root@autopkgtest:/etc/bind/maas# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether de:ad:be:ef:6b:b3 brd ff:ff:ff:ff:ff:ff
inet 10.245.136.6/21 brd 10.245.143.255 scope global ens4
valid_lft forever preferred_lft forever
inet6 fe80::dcad:beff:feef:6bb3/64 scope link
valid_lft forever preferred_lft forever
However, one IP is added for the internal domain that doesn't exist:
root@autopkgtest:/etc/bind/maas# cat zone.maas-internal
; Zone file modified: 2018-10-12 20:44:32.390833.
$TTL 15
@ IN SOA maas-internal. nobody.example.com. (
0000000127 ; serial
600 ; Refresh
1800 ; Retry
604800 ; Expire
15 ; NXTTL
)
@ 15 IN NS maas.
10-245-136-0--21 15 IN A 10.245.136.18
10-245-136-0--21 15 IN A 10.245.136.6
If we look at the db shell, we see:
autopkgtest | 1 | ens3 | physical | 52:54:00:12:34:56 | 10.245.136.18 | DISCOVERED | 10.245.136.0/21 | 0 | fabric-0
autopkgtest | 2 | ens4 | physical | de:ad:be:ef:6b:b3 | 10.245.136.6 | STICKY | 10.245.136.0/21 | 0 | fabric-0
********* A ver interesting thing, is that there's another machine in the subnet, with the same hostname that's actually causing the issue. |
MAAS is running in a VM with two interfaces. One of which doesn't have any ip addresses:
root@autopkgtest:/etc/bind/maas# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether de:ad:be:ef:6b:b3 brd ff:ff:ff:ff:ff:ff
inet 10.245.136.6/21 brd 10.245.143.255 scope global ens4
valid_lft forever preferred_lft forever
inet6 fe80::dcad:beff:feef:6bb3/64 scope link
valid_lft forever preferred_lft forever
However, one IP is added for the internal domain that doesn't exist:
root@autopkgtest:/etc/bind/maas# cat zone.maas-internal
; Zone file modified: 2018-10-12 20:44:32.390833.
$TTL 15
@ IN SOA maas-internal. nobody.example.com. (
0000000127 ; serial
600 ; Refresh
1800 ; Retry
604800 ; Expire
15 ; NXTTL
)
@ 15 IN NS maas.
10-245-136-0--21 15 IN A 10.245.136.18
10-245-136-0--21 15 IN A 10.245.136.6
If we look at the db shell, we see:
autopkgtest | 1 | ens3 | physical | 52:54:00:12:34:56 | 10.245.136.18 | DISCOVERED | 10.245.136.0/21 | 0 | fabric-0
autopkgtest | 2 | ens4 | physical | de:ad:be:ef:6b:b3 | 10.245.136.6 | STICKY | 10.245.136.0/21 | 0 | fabric-0
********* A ver interesting thing, is that there's another machine in the subnet, with potentially the same hostname ? |
|
| 2018-10-15 16:00:04 |
Andres Rodriguez |
maas: assignee |
|
Mike Pontillo (mpontillo) |
|
| 2018-10-16 20:35:59 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mpontillo/maas/+git/maas/+merge/356871 |
|
| 2018-10-17 01:18:12 |
MAAS Lander |
maas: status |
Triaged |
Fix Committed |
|
| 2018-10-27 05:12:51 |
Andres Rodriguez |
maas: milestone |
2.5.0rc1 |
2.5.0beta4 |
|
| 2018-10-27 05:16:49 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
