juju bootstrap fails with ipv6 global scope assigned addresses
Witold Krecicki
witold.krecicki at canonical.com
Wed Mar 28 16:04:44 UTC 2018
Hello,
Could you try to SSH to the newly created instance and, from there,
download https://streams.canonical.com/juju/tools/agent/2.3.4/juju-2.3.4-ubuntu-amd64.tgz
? It seems that it fails to download it.
--
Witold Krecicki
On Wed, Mar 28, 2018 at 5:56 PM, <christian.setzer at freies-franken.org> wrote:
> 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
>
>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
More information about the Juju
mailing list