Local provider does not respect tools-url

Bug #1235529 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Medium
Unassigned

Bug Description

I am testing the release of 1.15.1. Local provider does not find the tools I have uploaded. My test tools are at
    http://juju-dist.s3.amazonaws.com/testing/tools
    https://region-a.geo-1.objects.hpcloudsvc.com/vi/60502529753910/juju-dist/testing/tools
    https://jujutools.blob.core.windows.net/juju-tools/testing/tools
    file:///home/curtis/Work/new-tools/juju-dist/tools

Local provider does not recognise any of these as valid, though AWS, HP, and Azure do. It then insults me
    Juju cannot bootstrap because no tools are available for your environment.
    In addition, no tools could be located to upload.
    You may want to use the 'tools-url' configuration setting to specify the tools location.

I get this message also when I bootstrap like this and I can see that the two saucy and precise 1.15.1 tools are uploaded
    sudo juju --show-log bootstrap -e local --source=/home/curtis/Work/new-tools/juju-dist

I can bootstrap when I set the tools-url to
    tools-url: http://10.0.3.1:8040/tools
which is only deducible from from the --show-log where I see the --source is uploaded too.

Curtis Hovey (sinzui)
tags: added: local-provider
removed: local
Changed in juju-core:
importance: High → Medium
Revision history for this message
Curtis Hovey (sinzui) wrote :

the lxd provider does support streams

Changed in juju-core:
status: Triaged → Won't Fix
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.