juju-core 1.24.7
Milestone information
- Project:
- juju-core
- Series:
- 1.24
- Version:
- 1.24.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:
- 2 Andrew Wilkins, 1 Cheryl Jennings, 1 Eric Snow, 1 Menno Finlay-Smits, 3 Michael Foord, 4 Tim Penhey
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 12 Fix Released
Download files for this release
Release notes
# juju-core 1.24.7
A new stable release of Juju, juju-core 1.24.7, is now available.
This release replaces version 1.24.6.
## Getting Juju
juju-core 1.24.7 is available for Wily and backported to earlier
series in the following PPA:
https:/
Windows, Centos7, and OS X users will find installers at:
https:/
## Notable Changes
### The default EC2 instance is m3.medium
AWS deprecated the m1.* instance type. Juju now uses the m3.medium as
the default instance type when provisioning machines in EC2.
* m1.* instances will only be selected when specified using the
"instance-type" constraint.
* When no constraints are specified, the m3.medium type will be selected.
* When constraints are specified, m1 instance types which satisfy
the constraints will be ignored.
### Use the "storage" feature flag to try charms that support storage.
Storage was classified as experimental in 1.24, and has been found to be
problematic. Since storage is used implicitly by charms with default
stores, the feature was placed behind a feature flag. You can test
charms that support storage by bootstrapping a new environment with
"storage" enabled like so:
JUJU_
## Resolved issues
* Maas provider with maas 1.9 - /etc/network/
gets removed and bridge is not setup
Lp 1494476
* Switch default instance type from m1.small to t2.small/m3.medium
for ec2 provider
Lp 1373516
* Destroy-environment reports warning cannot delete security group
Lp 1335885
* Storage should be behind a feature flag in 1.24
Lp 1503740
* Configstore should break fslock if time > few seconds
Lp 1500613
* Config-changed error does not cause error state
Lp 1494542
* Setapihostports shouldn't record just one address per api server
Lp 1497094
* Failed worker can result in large number of goroutines and open
socket connections and eventually gets picked on by the oom killer
Lp 1496750
* Upgrade in progress reported, but panic happening behind scenes
Lp 1493123
* juju occasionally switches a units public-address if an additional
interface is added post-deployment
Lp 1435283
Finally
We encourage everyone to subscribe to the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
