Juju 1.25-beta1 is released

Aaron Bentley aaron.bentley at canonical.com
Wed Sep 30 14:31:45 UTC 2015


# juju-core 1.25-beta1

A new development release of Juju, juju-core 1.25-beta1, is now available.
This release replaces version 1.25-alpha1.


## Getting Juju

juju-core 1.25-beta1 is available for Wily and backported to earlier
series in the following PPA:

    https://launchpad.net/~juju/+archive/devel

Windows and OS X users will find installers at:

    https://launchpad.net/juju-core/+milestone/1.25-beta1

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.25-beta1.


## Notable Changes

This releases addresses stability and performance issues.

## Known issues

  * Deploying a service to a space which has no subnets causes the
    agent to panic
    Lp 1499426


## Resolved issues

  * Cloud-init fails when deploying centos with juju.
    Lp 1492066

  * Unit agent upgrade steps not run
    Lp 1494070

  * Juju status oneline format missing info
    Lp 1464679

  * M4 instance types not supported on aws
    Lp 1489477

  * Tabular format does not give enough details about machine
    provisioning errors
    Lp 1478156

  * Cmd/juju/storage: "volume list" yaml/json format is non-obvious
    Lp 1495338

  * Config-changed error does not cause error state
    Lp 1494542

  * Juju action-set skips values with underscore in the key
    Lp 1465844

  * Failed worker can result in large number of goroutines and open
    socket connections and eventually gets picked on by the oom killer
    Lp 1496750

  * Juju get incorrectly reports boolean default values
    Lp 1496639

  * Azure: units fail to attach block storage
    Lp 1498746

  * Error creating container juju-trusty-lxc-template; failed to parse
    config
    Lp 1485784

  * Upgrade in progress reported, but panic happening behind scenes
    Lp 1493123


Finally

We encourage everyone to subscribe the mailing list at
juju-dev at lists.canonical.com, or join us on #juju-dev on freenode.

Aaron Bentley



More information about the Juju mailing list