In the debug log there's an IP address of newly created instance, ssh ubuntu@ip should work, you might have to add -i your_juju_ssh_key
28.03.2018 19:03 <[email protected]> napisał(a): root@jujuadmin:~/.local/share/juju# cat controllers.yaml controllers: vctrl: uuid: 6a6e6e8f-f817-4774-8465-e458aee95fa1 api-endpoints: [] api endpoints is not set.. how do i ssh into the system? Quoting Witold Krecicki <[email protected]>: 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, <[email protected]> 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 [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
