Public bug reported:
Release: Xenial/16.04
MaaS version: 2.0.0+bzr5189-0ubuntu1~16.04.1
Local setup:
Internet -> 192.168.2.1/24 (GW) -> 192.168.2.19/24 (MaaS em0)
192.168.123.1 (MaaS em0.10)
In the end all interfaces on the MaaS host were static but before that
the untagged interface had been DHCP. For that reason there was a host
section in the DHCP server on the GW host that assigned a define IP
address to it.
With MaaS 2.0 the rack service will issue DHCP discover requests on all
detected interfaces every 10 minutes. The GW hosts tries to reply with
an address but doing so causes connectivity between GW and MaaS to be
disrupted. SSH connections to MaaS managed nodes in the 192.168.123.0/24
subnet do even time out (that could be because the DHCP server for that
subnet, which is managed by MaaS, is configured with a fix IP reply the
same way as the one on the GW host is).
For now I was able to work around this by adding "ignore bootp; ignore
booting;" statements to the DHCP host section on the GW host. That way I
loose the protection against misconfiguration but at least got a stable
connection between GW and MaaS.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637256
Title:
MaaS might disrupt network connectivity by probing DHCP services
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1637256/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
