juju bootstrap may try to compile binaries

[Jacek Nykis]

I installed juju from ppa:juju/stable:
juju-core 1.20.13-0ubuntu1~14.04.1~juju1
juju-local 1.20.13-0ubuntu1~14.04.1~juju1
juju-mongodb 2.4.9-0ubuntu3

Next I added a local environment to my environments.yaml and tried bootstrapping:
$ juju bootstrap
uploading tools for series [precise trusty]
Bootstrap failed, destroying environment
ERROR build command "go" failed: exit status 1; can't load package: package github.com/juju/juju/cmd/jujud: cannot find package "github.com/juju/juju/cmd/jujud" in any of:
 /usr/lib/go/src/pkg/github.com/juju/juju/cmd/jujud (from $GOROOT)
 ($GOPATH not set)

I am using trusty

[Curtis Hovey (sinzui)]

Do you also have golang and juju in your GOPATH installed? This behaviour only happens when juju thinks it is in a juju development env.

Juju requires an open network to get the agents for your local env. As you are on trusty, Juju will look to the cloud to find the precise agent. You can avoid the unneeded lookup in the cloud by by bootstrapping with the --upload-serie option
    juju boostrap --upload-series trusty

[Jacek Nykis (jacekn)]

At the time it happened I did have golang installed. I don't know what GOPATH was but I certainly did not set any environment variables.
Juju did have network access, I actually tried juju bootstrap on another VM and that worked.

I played with the broken env for a bit more and after wiping some golang packages it eventually worked so your theory about juju assuming dev env might be right.