Comment 4 for bug 1329429

The issue turned out to be root owned ~/.juju/environments from what I observed. This can be resolved by removing that directory and letting juju re-create the directory to warehouse the .jenv's with the proper permissions on bootstrap.

Can you give that a Go nuclearbob and let me know if the issue goes away?

Please note, you no longer need to use sudo to bootstrap *any* environment. If juju requires sudo rights, it will prompt you for an administrative password.