Comment 5 for bug 1307677

Revision history for this message
John A Meinel (jameinel) wrote :

Note that if I change my config to:
    localkvm:
        type: local
        container: kvm
        network-bridge: virbr0

I end up with:
$ juju status -e localkvm --debug
2014-04-24 11:42:41 INFO juju.cmd supercommand.go:296 running juju-1.19.1-trusty-amd64 [gc]
2014-04-24 11:42:41 DEBUG juju.conn api.go:193 no cached API connection settings found
2014-04-24 11:42:41 INFO juju.provider.local environprovider.go:40 opening environment "localkvm"
2014-04-24 11:42:41 DEBUG juju.container.kvm kvm.go:51 kvm-ok output:
INFO: /dev/kvm exists
KVM acceleration can be used

2014-04-24 11:42:41 DEBUG juju.provider.local environ.go:293 found "192.168.122.1" as address for "virbr0"
2014-04-24 11:42:41 DEBUG juju.provider.common state.go:74 waiting for DNS name(s) of state server instances [localhost]
2014-04-24 11:42:41 ERROR juju.container.kvm kvm.go:141 failed getting all instances: exit status 1
2014-04-24 11:42:41 DEBUG juju.provider.common state.go:79 error getting state instances: exit status 1
2014-04-24 11:42:41 ERROR juju.cmd supercommand.go:299 Unable to connect to environment "localkvm".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
exit status 1

I can see jujud running, and I can confirm that 192.168.122.1 is the local address for virbr0. However, this just isn't working.

Note that if I force the server address in the .jenv file the juju client panics when trying to connect.