Comment 1 for bug 1922891

PS: this might look like a duplicate of https://bugs.launchpad.net/maas/+bug/1744454 at first. But note that in my case MAAS has IP addresses on two different subnets, and it blends nameserver information together instead of keeping it separate for each subnet.

I just noticed that this isn't a problem with DHCP, but actually only happens when setting a static IP address in the node config and deploying. Then all six IP addresses end up in /etc/netplan/50-cloud-init.yaml, but via DHCP I only get the ones on 172.17.100 as it should be. So something must go wrong when MAAS composes the config for cloud-init I guess.