I successfully tested deploying 3 units of rabbitmq-server with the fix on MAAS 2.0.0 (beta5+bzr5026) with Juju 2.0-beta8-xenial-amd64 using 3 NUCs, each with multiple VLANs and 2 physical NICs. Here's the status output after settling: http://paste.ubuntu.com/16727654/ No hook errors were observed.
Also tried with 8 units on the LXD provider, one of which happened to get IPv6 address. This still caused a `hook failed: "cluster-relation-joined"` like described in bug 1574844, but the rest of the units are fine: http://paste.ubuntu.com/16727679/
I successfully tested deploying 3 units of rabbitmq-server with the fix on MAAS 2.0.0 (beta5+bzr5026) with Juju 2.0-beta8- xenial- amd64 using 3 NUCs, each with multiple VLANs and 2 physical NICs. Here's the status output after settling: http:// paste.ubuntu. com/16727654/ No hook errors were observed.
Also tried with 8 units on the LXD provider, one of which happened to get IPv6 address. This still caused a `hook failed: "cluster- relation- joined" ` like described in bug 1574844, but the rest of the units are fine: http:// paste.ubuntu. com/16727679/
Here are the logs from machine-7 in the paste above: http:// paste.ubuntu. com/16727698/ (machine-7.log) http:// paste.ubuntu. com/16727703/ (unit-rabbitmq- server- 6.log).