juju-core

  1. Series 1.20
  2. Bug #1436421
  3. Comment #5

Comment 5 for bug 1436421

Revision history for this message
Chris Stratford (chris-gondolin) wrote : Re: juju panics after upgrade from 1.18.4 to 1.20.11

Using 1.23-beta1 from http://ppa.launchpad.net/juju/devel/ubuntu/pool/main/j/juju-core/ I get this:

$ juju --debug status
2015-03-26 15:40:05 INFO juju.cmd supercommand.go:37 running juju [1.23-beta1-precise-amd64 gc]
2015-03-26 15:40:05 DEBUG juju.api api.go:176 no cached API connection settings found
2015-03-26 15:40:05 INFO juju.provider.openstack provider.go:241 opening environment "prod-cdo-ciaas"
2015-03-26 15:40:05 DEBUG juju.environs utils.go:94 StateServerInstances returned: [d8e0f90b-3b1f-4958-acd6-0cd74e45b99c]
2015-03-26 15:40:05 ERROR juju.cmd supercommand.go:430 Unable to connect to environment "prod-cdo-ciaas".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
config has no UUID

So, no panic now, but it still doesn't work (which I guess is progress).

One thing I have noticed: All the environments that fail are missing a ~/.juju-core/environments/thing.jenv file (not sure why, but some environments are there, some aren't)