juju-core 1.17.1
Milestone information
- Project:
- juju-core
- Series:
- 1.18
- Version:
- 1.17.1
- Released:
- Registrant:
- Curtis Hovey
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 2 Abel Deuring, 9 Andrew Wilkins, 1 Curtis Hovey, 1 Dimiter Naydenov, 4 Ian Booth, 2 John A Meinel, 2 Martin Packman, 1 Roger Peppe, 3 Tim Penhey, 2 William Reade
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 31 Fix Released
Download files for this release
Release notes
juju-core 1.17.1
A new development release of Juju, juju-core 1.17.1, is now available.
Getting Juju
juju-core 1.17.1 is available for trusty and backported to earlier
series in the following PPA:
https:/
Upgrading from stable releases to development releases is not supported. You
can upgrade test environments to development releases to test new features and
fixes, but it is not advised to upgrade production environments to 1.17.1.
If you are using a development release of juju-core, and find you need to go
back to a stable release, you can find it in the juju stable PPA:
https:/
If you have multiple source of juju-core, you can select the version you want
using apt:
sudo apt-get install juju-core=1.16.5*
New and Notable
* juju instances are now included in the "default" security group
Lp 1129720
* The sync-tools command no longer generates simple streams metadata for tools
See below.
* The bootstrap --source option was replaced with --metadata-source
See below.
Resolved issues
* juju-core broken with OpenStack Havana for tenants with multiple networks.
Lp 1241674
* juju destroy-environment no longer returns error when no environment exists
Lp 1225238
* Local provider isn't usable after an old environment has been destroyed
Lp 1238541
* Manual provider client cache prevents reuse of env by name
Lp 1238948
* destroy-environment no longer removes .jenv
Lp 1246343
* juju add-machine in trunk is incompatible with 1.16
Lp 1253631
* Error reading from streams.
Lp 1254401
* juju destroy-environment does not delete the local charm cache
Lp 1259925
* [manual] Manual bootstrap / provisioning does not add the ubuntu user
Lp 1261343
* [manual] Bootstrap fails if juju-run symlink already exists
Lp 1263586
* Ssh authorised keys written to wrong user
Lp 1263608
* Local provider reports wrong DNS name for machine, but right for unit
Lp 1269373
Known issues
* destroy-environment shutdown machines instead
Machines are soetimes shutdown instead of deleted after destroy-environment
was called. Use “destroy-
Lp 1272558
The sync-tools command no longer generates simple streams metadata for tools
The sync-tools command previously generated simple streams metadata for local
juju tools when provided with the --destination option. This is no longer the
case. You can create the simple streams metadata for tools thusly:
mkdir -p $MY_DIR/
mkdir -p $MY_DIR/
cp $PUBLIC_TOOLS/*tgz $MY_DIR/
juju metadata generate-tools -d $MY_DIR
Upload the tools directory to your private cloud. Set the tools-metadata-url in
the environment’s yaml to point to the tools URL.
The bootstrap --source option was replaced with --metadata-source
The juju bootstrap command previously accepted the --source option which was
the local path to a directory of juju tools. The bootstrap command now has a
--metadata-source that accepts the local path to simple streams metadata and
tools. If your workflow previously was to download the juju tools to a local
directory, then bootstrap with the --source option to upload the tools to your
environment, you need to call “juju metadata generate-tools” per the previous
example. See “juju help bootstrap” for more information.
Finally
We encourage everyone to subscribe the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
