case closed..
firewall rules were missing for those vlans..they havent been in use before.
Quoting Witold Krecicki :
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 napisał
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 napisał(a):
root@jujuadmin:~/.local/share/juju# cat controllers.yaml
controllers:
vctrl:
uuid: 6a6e6e8f-f817-4774-8465-e458aee95fa1
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 :
Hello,
Could you try to SSH to the newly created instanc
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, wrote:
> first i wanted to switch c
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 assign
