After talking this through with a few folks, it looks like this may be fixed in some version of juju. Adding "juju-origin: ppa" to environments.yaml makes the problem go away.
The issue remains in the stock version of juju for precise.
After talking this through with a few folks, it looks like this may be fixed in some version of juju. Adding "juju-origin: ppa" to environments.yaml makes the problem go away.
The issue remains in the stock version of juju for precise.