juju-core 1.17.2 A new development release of Juju, juju-core 1.17.2, is now available.
Getting Juju juju-core 1.17.2 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.2. 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.5* New and Notable * Bootstrapping the local-provider for lxc no longer requires sudo; it prompts for credentials as needed to bootstrap. See below. * Timeouts for bootstrap are configurable for environments that need more time to provision an instance. - bootstrap-timeout (default: 600s = 10m) - bootstrap-retry-delay (default: 5s) - bootstrap-addresses-delay (default: 10s) Lp 1257649 * The manual provider is now called “manual” in the juju config. “null” is an alias for “manual”. Lp 1272614 * If your cloud provides different OS image sets (released or daily for example), you can use the image-stream option in the config to select which will be used. Lp 1217397 Resolved issues * MAAS bootstrap errors Lp 1274547 * race: concurrent charm deployments corrupts deployments Lp 1067979 * juju status reports 'missing' instance-state when not run as root Lp 1237259 * juju-restore should have --description option Lp 1270481 * juju status polls all instances Lp 1272061 * null: machine addresses may override bootstrap hostname Lp 1274018 Known issues * destroy-environment shutdown machines instead Machines are sometimes shutdown instead of deleted after destroy-environment was called. Use “destroy-environment --force” to ensure machines are deleted. Lp 1272558 Bootstrapping the local-provider for lxc no longer requires sudo The juju bootstrap command cannot be run as root. Bootstrap will prompt for a password to use sudo as needed to setup the environment. This addresses several issues that arose because the owner and permissions of the local environment files were different from the owner of the process. The juju status command for example now reports the status of the machines without the need to run it with sudo. If you have used the local provider before, you may need to manually clean up some files that are still owned by root. The environment’s jenv file commonly needs to be removed. If your local environment is named “local” then there may be a local.jenv owned by root with the JUJU_HOME directory. After the local environment is destroyed, you can remove the file like this sudo rm ~/.juju/environments/local.jenv where “.juju” is the juju home directory and “local” is the environment name. 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-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
