juju-core 1.17.7
Milestone information
- Project:
- juju-core
- Series:
- 1.18
- Version:
- 1.17.7
- 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:
- 10 Andrew Wilkins, 1 Bodie Solomon, 1 Casey Marshall, 1 Curtis Hovey, 2 Dave Cheney, 2 Horacio Durán, 2 Ian Booth, 2 Tim Penhey, 1 Vladislav Klyachin, 1 Wayne Witzel III
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 24 Fix Released
Download files for this release
Release notes
juju-core 1.17.7
A new development release of Juju, juju-core 1.17.7, is now available.
Getting Juju
juju-core 1.17.7 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.7.
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 sources of juju-core, you can select the version
you want using apt:
sudo apt-get install juju-core=1.16.6*
New and Notable
* Juju retry-provisioning
* Juju unset-env
Resolved issues
* No debug-log with MAAS, 14.04 and juju-core 1.17.5
Lp 1294776
* Cannot destroy lxc env on trusty with juju-core 1.17.4-0ubuntu2
Lp 1296739
* Juju destroy-environment -y local --force does not stop jujud/mongod
processes on broken bootstrap
Lp 1292275
* Pressing control C during bootstrap leaves invalid .jenv file
Lp 1296475
* Manual provider fails to remove itself if bootstrapping fails
Lp 1296485
Juju retry-provisioning
You can use the retry-provisioning command in cases where deploying
services, adding units, or adding machines fails. The command allows you
to specify machines which should be retried to resolve errors reported
in status.
For example, after you deployed 100 units and machines, status reports
that machines 3, 27 and 57 could not be provisioned because of a rate
limit exceeded error. You can ask juju to retry:
juju retry-provisioning 3 27 5
Juju unset-env
The unset-env command allows you to reset one or more the environment
configuration attributes to its default value in a running Juju
instance. Attributes without defaults are removed, and attempting to
remove a required attribute with no default will result in an error.
Multiple attributes may be removed at once; keys are space-separated.
Finally
We encourage everyone to subscribe the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
