[00:20] <Beta_Tester> hi i am getting this: ERROR juju.worker.provisioner cannot start instance for machine "0/lxd/3": unable to setup network: host machine "0" has no available device in space(s) "int-api"
[00:22] <Beta_Tester> whenever i try to deploy to a defined space.  if i set it to a bad spaces name, the deploy command fails before submitting the task, so i know the sapce is defined. but somehow in the juju magic behind the scenes its not liking something.
[00:27] <Beta_Tester> i turned on juju debug-log (debug level) and watched it, no other errors pop up.. any ideas which logs to dig into? the space is a subnet x.x.112.0/22 network, and the the machine has an x.x.113.0/22 (yes mass auto-picked 113.0 as the IP) from a subnet perspective its valid... but wondering if that could be the issue?
[00:28] <Beta_Tester> the machine has a int-bn that has eth1 and eth2, and a bridge on top of the bond int-br, and then a vlan interface int-br.112
[00:30] <Beta_Tester> juju version: 2.6.5-bionic-amd64 and maas: 2.4.2
[02:20] <atdprhs> hello everyone, do anyone know why when juju deploys kubernetes, it resolves the dns to public ip address?
[02:21] <atdprhs> is there anyway that I can ssh into coredns/
[02:25] <atdprhs> everytime I try to ssh into coredns, it tells me that the pod is not found, but it's there
[14:13] <d4rks1d3> Hi
[15:27] <d4rks1d3> Someone around to help me with a keyston charm?
[15:27] <d4rks1d3> I am facing an error in the deployment time
[15:27] <d4rks1d3> that is not able to connect
[15:31] <d4rks1d3> https://pastebin.com/4caq4Kiz
[15:32] <d4rks1d3> here is the log
[15:32] <d4rks1d3> Thanks