Hi,
We are trying to use Juju Charms to deploy a network. We require each of
the charm to run in its own KVM. We are using Juju GUI (running on another
machine) to create a KVM container on the node and start the charm.
However, we observe that charm is stuck at agent initialization. We are
able t
My initial thought is that we aren't getting KVM onto a bridge to the outer
network properly. One thought that you could try is to first deploy and
LXC/LXD container onto machine 26 and then do the KVM. This is simply
because I know we've spent a lot more time getting container networking
right, an
To isolate issues you can always just try deploying the "ubuntu" charm, and
see if it comes up correctly. For further debugging I would ssh onto the
outer machine (juju ssh 26 in this case) and see how things are configured.
You can look at /var/log/juju/machine*.log. And get the output of things
l
Hi,
I tried with ubuntu charm and the issue is still reproducible. I tried
creating a container first and then KVM. But behavior seems to be similar.
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS
PUBLIC-ADDRESS MESSAGE
juju-gui/0 unknownidle1.25.3 080/
I fixed a bug last week where KVM containers were using the wrong parent
device:
https://bugs.launchpad.net/juju-core/+bug/1563853
This would definitely have been a problem if you were using more than one
NIC.
On 3 April 2016 at 08:19, John Meinel wrote:
> My initial thought is that we aren'
