error: no CA certificate in environment configuration

[Sidnei da Silva]

Steps to reproduce:

Run juju bootstrap on machine 1
Run juju status on machine 2

Since machine 2 doesn't have the .pem credentials for the environment, the message above is printed. It doesn't give any hint as to what could be done to provide the expected ca certificates and where they are expected to be found.

[Colin Watson (cjwatson)]

This also seems to happen on upgrade from Python juju to juju-core. No indication of how I'm supposed to resolve it and recover my existing deployment.

[John A Meinel (jameinel)]

There isn't (currently) an "upgrade" method to go from python-juju to juju-core. @Colin can you describe the steps you tried to take?

We have some patches coming online to make it clearer if you are trying to mix the environments (since they are not compatible), and I think there is a different bug about creating something that would let you migrate, though I don't think it is being actively worked on at the moment.

[John A Meinel (jameinel)]

To comment on the bug itself, you need more than just environments.yaml in ~/.juju. The certificate files are also present there.

I believe if you copy all of ~/.juju across to the second machine, then 'juju status' will work correctly. (IOW, juju needs more than just environments.yaml, but everything it needs should be in the ~/.juju directory.)

[Cheryl Jennings (cherylj)]

This is addressed in Juju 2.0 by using `juju add-user` and `juju register` to share connection information about a particular controller.