juju-core 1.17.3 A new development release of Juju, juju-core 1.17.3, is now available.
Getting Juju juju-core 1.17.3 is available for trusty and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel 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.3. 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://launchpad.net/~juju/+archive/stable 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 “run” executes arbitrary commands on some or all instances Resolved issues * MaaS provider can't bootstrap on precise with 1.17.2 because wget on precise cannot talk to streams.canonical.com over SSL Lp 1282553 * Version of django in cloud-tools conflicts with horizon:grizzly Lp 1240667 * Juju 1.17.x cannot destroy a 1.16.5 azure environment Lp 1277636 * Manual provider bootstrap fails if ubuntu user is not initialised Lp 1279259 * Local provider writes into /etc/apt/apt.conf.d on the host Lp 1279554 * Manual provider bootstrap fails with "102 bootstrapping failed, removing state file: exit status 1" Lp 1282235 * Juju deploys wrong machine when no machine matching constraints is available Lp 1237163 * juju-deployer teardown fails due to hook errors Lp 1244807 * Juju ssh exits with sub command returncode Lp 1246938 * Juju sync-tools does not support --destination Lp 1247175 * Juju switch -l does not return list of env names Lp 1250285 * Stack trace with manual provider when add-machine is called Lp 1262764 * Manual provider environment disregards admin-secret in environments.yaml Lp 1263900 * Juju run --no-context fails on machine without units Lp 1272112 * JUJU_HOME not honoured when destroying local env Lp 1273408 * putcharm api fails for compressed charm contents wrapped in a folder Lp 1273464 * Local provider does not prevent units on machine 0 anymore Lp 1273933 * Creation of LXC bridge in 1.17.0 fails Lp 1274210 Juju “run” executes arbitrary commands on some or all instances. he “run” command can be used by devops or scripts to inspect or do work on services, units, or machines. Commands for services or units are executed in a hook context. Charm authors can use the “run” command to develop and debug scripts that run in hooks. For example, to run “uname” on every instance: juju run "uname -a" --all Or to run uptime on some instances: juju run "uptime" --machine=2 juju run "uptime" --service=mysql See “juju run --help” for more details Finally We encourage everyone to subscribe the mailing list at [email protected], or join us on #juju-dev on freenode. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
