Fixed lp:1308146 - backported from trunk
Merge pull request #790 from dimitern/lp-1308146-1.20-backport

Fixed lp:1308146 - backported from trunk

See http://pad.lv/1308146 - this fixes the issue by backporting
the already landed fix from trunk (#786).
Bump juju/charm dependency to purge old goyaml import
Increment juju to 1.20.9
Merge pull request #800 from sinzui/inc-1.20.9

Increment juju to 1.20.9

Update juju and Win installer to 1.20.9
Merge pull request #791 from bz2/1.20_dep_charm_yaml

Bump juju/charm dependency to purge old goyaml import

Building juju was still pulling in launchpad.net/goyaml - as well as the newer gopkg.in/yaml.v1 location.

Fixed in the 1.20 branch of charm by <https://github.com/juju/charm/pull/48>, this change just bumps the dependency to require that.
Add apt_preferences file with bootcmd

The apt_preferences file must be written
before we run "apt-get upgrade", or the
pinning does not take effect on non-bootstrap
machines.

Fixes https://bugs.launchpad.net/juju-core/+bug/1370781
Merge pull request #813 from axw/lp1370781-upgradejuju-pinned-1.20

Add apt_preferences file with bootcmd

The apt_preferences file must be written
before we run "apt-get upgrade", or the
pinning does not take effect on non-bootstrap
machines.

Fixes https://bugs.launchpad.net/juju-core/+bug/1370781
Increment juju to 1.20.10
Add new location of gocheck which some dependencies pull in already
Merge pull request #867 from bz2/1.20_dep_gocheck

Add new location of gocheck which some dependencies pull in already
Merge pull request #862 from sinzui/inc-1.20.10

Increment juju to 1.20.10

Increment juju stable to 1.20.10.
Increment juju to 1.20.11
Merge pull request #881 from sinzui/inc-1.20.11

Increment juju to 1.20.11

Increment Juju stable to 1.20.11
Use tmp location for tool cache to avoid issues deleting machines
Merge pull request #929 from wallyworld/local-tools-location

Use tmp location for tool cache to avoid issues deleting machines

When starting an LXC container for the local provider, if we put the tools tarballs in a bind mounted dir which lives under /var/lib/juju, the contents of this dir are deleted when the agent exits on machine deletion. Thus subsequent containers can't find tools. So we use a tmp dir instead.

Fixes: https://bugs.launchpad.net/juju-core/1.20/+bug/1379802
Merge pull request #930 from wallyworld/better-openstack-az-placement

Cycle through azs till we find one that works

Update the openstack provider to behave more like ec2. If an attempt to start an instance on an availability zone fails because openstack says there are no available hosts, then try another zone till we find one that works. The provider previously just picked the first zone and didn't try any others.

Fixes: https://bugs.launchpad.net/juju-core/+bug/1380557
Merge pull request #932 from wallyworld/better-openstack-az-placement-1.20

Merge pull request #930 from wallyworld/better-openstack-az-placement

Cycle through azs till we find one that works

Update the openstack provider to behave more like ec2. If an attempt to start an instance on an availability zone fails because openstack says there are no available hosts, then try another zone till we find one that works. The provider previously just picked the first zone and didn't try any others.

Fixes: https://bugs.launchpad.net/juju-core/+bug/1380557
Fix for broken tests when new Ubuntu series is released.
Merge pull request #959 from anastasiamac/1.20_fake-distro

Fix for broken tests when new Ubuntu series is released.

Bug https://bugs.launchpad.net/juju-core/1.20/+bug/1384175