Merge lp:~jameinel/juju-core/1.18-local-trusty-and-precise-1306537 into lp:juju-core/1.18
Proposed by
John A Meinel
Status: | Rejected |
---|---|
Rejected by: | John A Meinel |
Proposed branch: | lp:~jameinel/juju-core/1.18-local-trusty-and-precise-1306537 |
Merge into: | lp:juju-core/1.18 |
Diff against target: |
17 lines (+7/-0) 1 file modified
cmd/juju/bootstrap.go (+7/-0) |
To merge this branch: | bzr merge lp:~jameinel/juju-core/1.18-local-trusty-and-precise-1306537 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+216888@code.launchpad.net |
Description of the change
bootstrap: always provider precise and trusty
Now that we have 2 potential LTS targets, when we bootstrap the local
provider, make sure we upload tools for both of them. That way when
deploying charms, we can successfully deploy all the stable charms.
This addresses bug #1306537, perhaps as a band-aid but I think a
reasonable one.
To post a comment you must log in.
Note, there aren't any tests for this because I couldn't find any tests for the local provider behavior of forcing --upload-tools. So I punted.