juju bootstrap does not honor https_proxy in environment when fetching tools

Bug #1240260 reported by Steve Conklin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Tim Penhey
juju-core (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When trying to run 'juju bootstrap', it failed with the following:

$ juju bootstrap
WARNING no tools available, attempting to retrieve from https://juju-dist.s3.amazonaws.com/
ERROR Get https://juju-dist.s3.amazonaws.com/: dial tcp 176.32.99.35:443: connection timed out

This subnet does not have access to the outside world except through a proxy. Specifying the proxy as follows did not solve the problem:

export https_proxy="http://squid.internal:3214" ; juju bootstrap

However, wget worked after that - so wget honors the proxy but juju does not.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: juju-core 1.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Tue Oct 15 22:32:15 2013
Dependencies:
 gcc-4.8-base 4.8.1-10ubuntu8
 libc6 2.17-93ubuntu4
 libgcc1 1:4.8.1-10ubuntu8
 multiarch-support 2.17-93ubuntu4
MarkForUpload: True
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Steve Conklin (sconklin) wrote :
James Page (james-page)
Changed in juju-core (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Andrew Wilkins (axwalk) wrote :

You should be able to just set http_proxy, and have that work. Go will honour http_proxy, and do the usual CONNECT method. But, depends on whether you specifically don't want to proxy HTTP traffic.

We'll need to make changes to our code to support both http_proxy and https_proxy, or wait for Go to support it.
https://code.google.com/p/go/issues/detail?id=6181

Curtis Hovey (sinzui)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
Curtis Hovey (sinzui)
tags: added: cts-cloud-review
Revision history for this message
Dave Cheney (dave-cheney) wrote :

I'm pretty sure this is fixed.

Changed in juju-core:
milestone: none → 1.18.0
Ian Booth (wallyworld)
Changed in juju-core:
assignee: nobody → Tim Penhey (thumper)
status: Triaged → Fix Released
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.18.0 → 1.17.3
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 1.17.6-0ubuntu1

---------------
juju-core (1.17.6-0ubuntu1) trusty; urgency=medium

  * New upstream point release, including fixes for:
    - br0 not bought up by cloud-init with MAAS provider (LP: #1271144).
    - ppc64el enablement for juju/lxc (LP: #1273769).
    - juju userdata should not restart networking (LP: #1248283).
    - error detecting hardware characteristics (LP: #1276909).
    - juju instances not including the default security group (LP: #1129720).
    - juju bootstrap does not honor https_proxy (LP: #1240260).
  * d/control,rules: Drop BD on bash-completion, install bash-completion
    direct from upstream source code.
  * d/rules: Set HOME prior to generating man pages.
  * d/control: Drop alternative dependency on mongodb-server; juju now only
    works on trusty with juju-mongodb.
 -- James Page <email address hidden> Mon, 24 Mar 2014 16:05:44 +0000

Changed in juju-core (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.