Looking at the very first pastebin:
2016-07-14 10:10:00 INFO worker.uniter.jujuc server.go:173 running hook tool "relation-get" ["--format=json" "hostname"]
2016-07-14 10:10:00 INFO cloud-compute-relation-changed Traceback (most recent call last):
...
2016-07-14 10:10:00 INFO cloud-compute-relation-changed File "/usr/lib/python2.7/dist-packages/dns/resolver.py", line 910, in query
2016-07-14 10:10:00 INFO cloud-compute-relation-changed raise NXDOMAIN
2016-07-14 10:10:00 INFO cloud-compute-relation-changed dns.resolver.NXDOMAIN
Hints that it might even be something else that is failing. Something about how we are telling MAAS about the multiple IP addresses for a container might cause MAAS to get confused and not able to return the normal hostname for one of the secondary addresses.
Looking at the very first pastebin: relation- changed Traceback (most recent call last): relation- changed File "/usr/lib/ python2. 7/dist- packages/ dns/resolver. py", line 910, in query relation- changed raise NXDOMAIN relation- changed dns.resolver. NXDOMAIN
2016-07-14 10:10:00 INFO worker.uniter.jujuc server.go:173 running hook tool "relation-get" ["--format=json" "hostname"]
2016-07-14 10:10:00 INFO cloud-compute-
...
2016-07-14 10:10:00 INFO cloud-compute-
2016-07-14 10:10:00 INFO cloud-compute-
2016-07-14 10:10:00 INFO cloud-compute-
Hints that it might even be something else that is failing. Something about how we are telling MAAS about the multiple IP addresses for a container might cause MAAS to get confused and not able to return the normal hostname for one of the secondary addresses.