juju-core 1.24-beta6
Milestone information
- Project:
- juju-core
- Series:
- 1.24
- Version:
- 1.24-beta6
- 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:
- 3 Anastasia, 1 Andrew Wilkins, 1 Cheryl Jennings, 2 Horacio Durán, 10 Ian Booth, 3 Jesse Meek, 3 Nate Finch, 1 William Reade
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 24 Fix Released
Download files for this release
Release notes
# juju-core 1.24-beta6
A new development release of Juju, juju-core 1.24-beta6, is now available.
This release replaces version 1.24-beta5.
## Getting Juju
juju-core 1.24-beta6 is available for vivid and backported to earlier
series in the following PPA:
https:/
Windows and OS X users will find installers at:
https:/
Development releases use the "devel" simple-streams. You must configure
the `agent-stream` option in your environments.yaml to use the matching
juju agents.
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.24-beta6.
## Notable Changes
This releases addresses stability and performance issues.
## Resolved issues
* Intermittent panic: rescanned document
Lp 1449054
* `juju upgrade-juju --upload-tools` leaves local environment
unusable
Lp 1457728
* warning: log line attempted over max size - leadership related
Lp 1457645
* Debug-log eof: invalid tag and panic seen in state server logs
Lp 1461354
* Juju has conf files in /var/log/juju on instances
Lp 1370896
* Juju restore fails with "/var/lib/
directory"
Lp 1431372
* Cannot destroy-environment with 'juju user add' .jenv file
Lp 1403165
* Juju cannot create vivid containers
Lp 1442308
* State: availability zone upgrade fails if containers are present
Lp 1441478
* 1.23.2.1, mongo: document is larger than capped size
Lp 1454891
* "relation-set --file -" doesn't seem to work
Lp 1454678
* Maas provider doesn't know about "failed deployment" instance
status
Lp 1376246
* Juju status --utc does not display utc and is confused
Lp 1459611
* Juju agent opens api when upgrade is pending
Lp 1459912
* 'juju status' wall clock timestamps should display offset not tz
abbrev
Lp 1459616
* Harvest mode setting not used by container provisioner
Lp 1459885
* Allow status-set/get to a service by its leader unit
Lp 1461111
* Unit storage add should only accept count as constraint
Lp 1461342
Finally
We encourage everyone to subscribe the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
