juju bootstrap fails with ipv6 global scope assigned addresses

[christian.setzer at freies-franken.org]

first i wanted to switch completly to ipv6 but since this is not  
supported i enabled ipv4 again in those vlan's which should be used  
for juju kubernetes clusters. ok so the bootstrapped controller seems  
to get an ipv4 address from the dhcp pool. but also gets an ipv6  
address which is assigned via router adverstisement (i cant turn that  
off complety). so from tcp/ip protocoll persepective ipv6 has  
precedence over ipv4. the initial connection to get the vmdk file from  
the website works via ipv6 connection. but then.. please take a look  
at the log.

is there something i can do? or wait until the devs have enabled ipv6?

BR

Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20180328/f4c3467a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: juju_bootstrap_ipv6_debug.out
Type: application/octet-stream
Size: 54557 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju/attachments/20180328/f4c3467a/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1730 bytes
Desc: PGP Public Key
URL: <https://lists.ubuntu.com/archives/juju/attachments/20180328/f4c3467a/attachment.key>