juju bootstrap fails when http_proxy is set in environments.yaml

[Corey Bryant]

juju bootstrap fails when http_proxy is set in environments.yaml

juju-core version: 1.22-beta5-0ubuntu1~14.04.1~juju1 0

juju bootstrap errors with:
"2015-03-12 10:55:01 ERROR juju.cmd supercommand.go:411 no instances found"

See console log attachment for more details.

[Curtis Hovey (sinzui)]

Are you also setting proxy settings in the shell env when bootstrapping? A common reason bootstraps fail when a proxy is needed is because bootstraping using the shell env vars, then once the environment is bootstrapped the settings in the config are used. And it is common for the values on the host bootstraping to be different from the setting in the yaml.

[Corey Bryant (corey.bryant)]

I'm not setting any proxy settings in the shell env when bootstrapping. I assume I shouldn't be.

[Curtis Hovey (sinzui)]

We need more information. Please use --debug to capture what juju is trying to do:
    juju --debug bootstrap --upload-tools

[Corey Bryant (corey.bryant)]

I'm pretty sure this isn't a juju bug. 'nova list' can't find the keystone endpoint when http_proxy env var is set on serverstack, without juju involved. So I'm going to mark this invalid.