<p dir="ltr">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, and we could have a bug where we are assuming a bridge that we only set up for containers.</p>
<p dir="ltr">John<br>
=:-></p>
<div class="gmail_quote">On Apr 2, 2016 11:57 PM, "phani shankar" <<a href="mailto:phanishankarpr@gmail.com">phanishankarpr@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>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 to bring up the charm in the root container. Can you please guide us on how we can debug it further.</div><div><br></div><div>juju-debug-log indicates that there was an error fetching public address and there was a broken pipe. Juju GUI is running on 10.214.2.61 and node on which we are installing the charm is in 10.214.2.127</div><div><div><br></div><div>juju-debug-log <br></div><div>==========</div><div>machine-0: message repeated 3 times: [2016-04-02 19:29:05 ERROR juju.rpc server.go:573 error writing response: write tcp <a href="http://10.214.2.127:53794" target="_blank">10.214.2.127:53794</a>: broken pipe]</div><div>machine-0: 2016-04-02 19:38:50 WARNING juju.state allwatcher.go:351 getting a public address for unit "oai-hss/7" failed: "public no address"</div><div>machine-0: 2016-04-02 19:38:50 WARNING juju.state allwatcher.go:355 getting a private address for unit "oai-hss/7" failed: "private no address"</div><div>machine-0: 2016-04-02 19:39:37 WARNING juju.apiserver.client status.go:465 error fetching public address: "public no address"</div><div>machine-0: 2016-04-02 19:39:37 WARNING juju.apiserver.client status.go:677 error fetching public address: public no address</div><div><br></div><div>Outcome of juju status:</div><div>=================</div><div><br></div><div><div>crossmobile@cm-mainserver-juju:~$ juju status --format=tabular</div><div>[Services]</div><div>NAME STATUS EXPOSED CHARM</div><div>juju-gui unknown true cs:trusty/juju-gui-52</div><div>mysql unknown false cs:trusty/mysql-36</div><div>oai-enb blocked false local:trusty/oai-enb-23</div><div>oai-hss unknown false local:trusty/oai-hss-5</div><div><br></div><div>[Units]</div><div>ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE</div><div>juju-gui/0 unknown idle 1.25.3 0 80/tcp,443/tcp cm-mainserver-juju</div><div>mysql/1 unknown idle 1.25.3 5 3306/tcp 10.214.2.125</div><div>oai-enb/10 blocked idle 1.25.3 21 2152/udp 10.214.2.135 Waiting for EPC relation</div><div>oai-hss/7 unknown allocating 26/kvm/1 Waiting for agent initialization to finish</div><div><br></div><div>[Machines]</div><div>ID STATE VERSION DNS INS-ID SERIES HARDWARE</div><div>0 started 1.25.3 cm-mainserver-juju manual: trusty arch=amd64 cpu-cores=1 mem=3942M</div><div>5 started 1.25.3 10.214.2.125 manual:10.214.2.125 trusty arch=amd64 cpu-cores=1 mem=3942M</div><div>21 started 1.25.3 10.214.2.135 manual:10.214.2.135 trusty arch=amd64 cpu-cores=4 mem=15677M</div><div>26 started 1.25.3 10.214.2.127 manual:10.214.2.127 trusty arch=amd64 cpu-cores=1 mem=3942M</div></div><div><br></div><div><br></div><div>Please let me know your thoughts.</div><div><br></div><div>PHANI SHANKAR</div>
</div></div>
<br>--<br>
Juju-dev mailing list<br>
<a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
<br></blockquote></div>