juju-core 1.19.0

Milestone information

Project:
juju-core
Series:
1.20
Version:
1.19.0
Released:
2014-04-15  
Registrant:
Curtis Hovey
Release registered:
2014-04-15
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
2 Abel Deuring, 8 Andrew Wilkins, 4 Casey Marshall, 1 Curtis Hovey, 9 Dave Cheney, 1 Dimiter Naydenov, 1 Horacio Durán, 6 Ian Booth, 1 Jason Hobbs, 3 Jesse Meek, 10 John A Meinel, 1 Matthew Williams, 1 Nate Finch, 12 Tim Penhey, 1 William Reade
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
61 Fix Released

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon juju-setup-1.19.0.exe (md5, sig) Windows installer for the juju client 11
last downloaded 108 weeks ago
download icon juju-core_1.19.0.tar.gz (md5, sig) Juju-core release 15
last downloaded 108 weeks ago
Total downloads: 26

Release notes 

juju-core 1.19.0

A new development release of Juju, juju-core 1.19.0, is now available.

Getting Juju

juju-core 1.19.0 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.19.0.

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.18.1*

New and Notable

* Juju debug-log command supports filtering and works with lxc

* Juju supports Azure availability sets

Resolved issues

* Juju MUST not strip binaries
  Lp 1301719

* Manual provisioned systems stuck in pending on arm64
  Lp 1302205

* Version reports "armhf" on arm64
  Lp 1304742

* Use network tags in the API
  Lp 1304905

* Juju destroy-environment on openstack should remove sec groups
  Lp 1227574

* Bootstrapping juju from within a juju deployed unit fails
  Lp 1285256

* Restarting API server with lots of agents gets hung
  Lp 1290843

* Manual provisioning requires target hostname to be directly resolvable
  Lp 1300264

* Local provider behaves poorly when juju-mongodb is not installed
  on trusty
  Lp 1301538

* Juju deploy --to lxc:0 cs:trusty/ubuntu creates precise container
  Lp 1302820

* Nasty worrying output using local provider
  Lp 1304132

* Intermittent error destroying local provider environments
  Lp 1307290

Juju debug-log command supports filtering and works with lxc

The "debug-log" command shows the consolidate logs of all juju agents
running on all machines in the environment. The command operates like
"tail -f" to stream the logs to the your terminal. The feature now
support local-provider LXC environments. Several options are available
to select which log lines to display.

The "lines" and "limit" options allow you to select the starting log
line and how many additional lines to display. The default behaviour is
to show the last 10 lines of the log. The "lines" option selects the
starting line from the end of the log. The "limit" option restricts the
number of lines to show. For example, you can see just 20 lines from
last 100 lines of the log like this:
    juju debug-log --lines 100 --limit 20

There are many ways to filter the juju log to see just the pertinent
information. A juju log line is written in this format:
    <entity> <timestamp> <log-level> <module>:<line-no> <message>

The "include" and "exclude" options select the entity that logged the
message. An entity is a juju machine or unit agent. The entity names are
similar to the names shown by "juju status". You can exclude all the log
messages from the bootstrap machine that hosts the state-server like
this:
    juju debug-log --exclude machine-0

The options can be used multiple times to select the log messages. This
example selects all the message from a unit and its machine as reported
by status:
    juju debug-log --include unit-mysql-0 --include machine-1

The "level" option restricts messages to the specified log-level or
greater. The levels from lowest to highest are TRACE, DEBUG, INFO,
WARNING, and ERROR. The WARNING and ERROR messages from the log can seen
thusly:
    juju debug-log --level WARNING

The "include-module" and "exclude-module" are used to select the kind of
message displayed. The module name is dotted. You can specify all or
some of a module name to include or exclude messages from the log. This
example progressively excludes more content from the logs
    juju debug-log --exclude-module juju.state.apiserver
    juju debug-log --exclude-module juju.state
    juju debug-log --exclude-module juju

The "include-module" and "exclude-module" options can be used multiple
times to select the modules you are interested in. For example, you can
see the juju.cmd and juju.worker messages like this:
    juju debug-log --include-module juju.cmd --include-module juju.worker

The "debug-log" command output can be piped to grep to filter the
message like this:
    juju debug-log --lines 500 | grep amd64

You can learn more by running "juju debug-log --help" and "juju help
logging"

Juju supports Azure availability sets

Azure environments can be configured to use availability sets. This
feature ensures services are distributed for high availability; as long
as at least two units are deployed, Azure guarantees 99.95% availability
of the service overall. Exposed ports will be automatically load
balanced across all units within the service.

New Azure environments will have support for availability sets by
default. To revert to the previous behaviour, the
"availability-sets-enabled" option must be set in environments.yaml like
so:
    availability-sets-enabled: false

Placement is disabled when "availability-sets-enabled" is true. The
option cannot be disabled after the environment is bootstrapped.

Finally

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

Changelog 

This release does not have a changelog.

0 blueprints and 61 bugs targeted

Bug report Importance Assignee Status
1301719 #1301719 juju MUST not strip binaries 2 Critical Dave Cheney  10 Fix Released
1302205 #1302205 manual provisioned systems stuck in pending on arm64 2 Critical Ian Booth  10 Fix Released
1304742 #1304742 version reports "armhf" on arm64 2 Critical Ian Booth  10 Fix Released
1304905 #1304905 Change NetworkName to NetworkId across codebase and use network tags in the API 2 Critical Dimiter Naydenov  10 Fix Released
1306212 #1306212 juju bootstrap fails with local provider 2 Critical John A Meinel  10 Fix Released
1306358 #1306358 upgrade-juju doesn't for all providers 2 Critical Nate Finch  10 Fix Released
1307450 #1307450 upgrading from 1.18.1 to 1.19 (trunk) fails (API server stops responding) 2 Critical John A Meinel  10 Fix Released
1307836 #1307836 Ci unititests fail on precise 2 Critical Curtis Hovey  10 Fix Released
1190953 #1190953 debug-log cannot filter messages 3 High Tim Penhey  10 Fix Released
1202682 #1202682 debug-log doesn't work with lxc provider 3 High Tim Penhey  10 Fix Released
1212542 #1212542 cmd/juju: debug-log should not take additional arguments 3 High Tim Penhey  10 Fix Released
1217595 #1217595 security groups reused without ensuring validity 3 High Abel Deuring  10 Fix Released
1227036 #1227036 debug-log is unusable 3 High Tim Penhey  10 Fix Released
1227574 #1227574 destroy-env on openstack should remove sec groups 3 High Abel Deuring  10 Fix Released
1229411 #1229411 Juju on Azure does not support Availability Sets 3 High Andrew Wilkins  10 Fix Released
1240146 #1240146 Azure Provider: Utilize Azure's delete API 3 High Andrew Wilkins  10 Fix Released
1251076 #1251076 rpc: TestChangeAPI hits an assertion error with gccgo 3 High Dave Cheney  10 Fix Released
1260480 #1260480 juju test suite fails if bzr whoami is unset 3 High Tim Penhey  10 Fix Released
1282690 #1282690 ensure joyent provider gets included in 1.18 release 3 High Ian Booth  10 Fix Released
1285256 #1285256 bootstrapping juju from within a juju deployed unit fails 3 High Matthew Williams  10 Fix Released
1285410 #1285410 juju names arm arch 'arm' internally, but 'armhf' in tools 3 High Jason Hobbs  10 Fix Released
1290824 #1290824 juju should ask the charm store to decide the default series for a charm 3 High Casey Marshall  10 Fix Released
1290843 #1290843 restarting API server with lots of agents gets hung 3 High John A Meinel  10 Fix Released
1291022 #1291022 Cannot restore a state-server on ec2 and openstack 3 High Horacio Durán  10 Fix Released
1294931 #1294931 juju ssh/scp/debug-log/debug-hooks requires a direct, public IP for each machine 3 High Andrew Wilkins  10 Fix Released
1295140 #1295140 Trusty juju-mongodb doesn't support js for the juju-store 3 High Casey Marshall  10 Fix Released
1298703 #1298703 state: multiple test failures 3 High Dave Cheney  10 Fix Released
1298708 #1298708 bzr: bzr unit tests are not properly isolated 3 High Tim Penhey  10 Fix Released
1298770 #1298770 instance: NewAddress{,es} is a footgun 3 High Dave Cheney  10 Fix Released
1298789 #1298789 state/apiserver/client: wrong scope for public address in test 3 High Dave Cheney  10 Fix Released
1299588 #1299588 LXC permission denied issue with 1.17.7 3 High Ian Booth  10 Fix Released
1299802 #1299802 upgrade-juju 1.16.6 -> 1.18 (tip) fails 3 High John A Meinel  10 Fix Released
1299958 #1299958 worker/peergrouper: test failure 3 High Dave Cheney  10 Fix Released
1299969 #1299969 launchpad.net/juju-core/provider/manual: ssh tests are not properly isolated 3 High Jesse Meek  10 Fix Released
1300264 #1300264 manual provisioning requires target hostname to be directly resolvable 3 High Andrew Wilkins  10 Fix Released
1300321 #1300321 manual provider bootstrap fails if curl isn't installed 3 High John A Meinel  10 Fix Released
1300530 #1300530 state/apiserver/provisioner: gccgo test failure 3 High Dave Cheney  10 Fix Released
1300538 #1300538 state/apiserver/firewaller: gccgo test failure 3 High Dave Cheney  10 Fix Released
1300846 #1300846 Juju crashes bootstrapping joyent 3 High John A Meinel  10 Fix Released
1300889 #1300889 azure and hp cannot deploy as of r2524 3 High Andrew Wilkins  10 Fix Released
1301315 #1301315 joyent provider uses "key-file" rather than "private-key-path" for config entry 3 High John A Meinel  10 Fix Released
1301538 #1301538 local provider behaves poorly when juju-mongodb is not installed on trusty 3 High Jesse Meek  10 Fix Released
1302820 #1302820 juju deploy --to lxc:0 cs:trusty/ubuntu creates precise container 3 High Tim Penhey  10 Fix Released
1303697 #1303697 peer relation disappears during upgrade of juju 3 High William Reade  10 Fix Released
1303735 #1303735 public-address change to internal bridge post juju-upgrade 3 High Andrew Wilkins  10 Fix Released
1303880 #1303880 Juju 1.18.0, can not deploy local charms without series 3 High Casey Marshall  10 Fix Released
1304132 #1304132 nasty worrying output using local provider 3 High Ian Booth  10 Fix Released
1304135 #1304135 panic: runtime error: index out of range 3 High Tim Penhey  10 Fix Released
1304340 #1304340 DesiredVersion should not return versions newer than API Server 3 High John A Meinel  10 Fix Released
1304767 #1304767 test failure in cmd/juju 3 High Jesse Meek  10 Fix Released
1304770 #1304770 store: tests do not pass with juju-mongodb 3 High Casey Marshall  10 Fix Released
1305397 #1305397 provider/common: test failure 3 High Dave Cheney  10 Fix Released
1306208 #1306208 juju scp no longer allows multiple extra arguments to pass through 3 High John A Meinel  10 Fix Released
1306296 #1306296 juju cannot downgrade to same major.minor version with earlier patch number 3 High John A Meinel  10 Fix Released
1306328 #1306328 debug-log limit with backlog broken 3 High Tim Penhey  10 Fix Released
1306902 #1306902 machine-0 agent needs admin rights during upgrade 3 High Andrew Wilkins  10 Fix Released
1307290 #1307290 Intermittent error destroying local provider environments 3 High Tim Penhey  10 Fix Released
1223901 #1223901 provider/azure: tests are racy 4 Medium Andrew Wilkins  10 Fix Released
1190950 #1190950 debug-log cannot show history 5 Low Tim Penhey  10 Fix Released
1221015 #1221015 ctrl-c fails to stop debug-log 5 Low Tim Penhey  10 Fix Released
1221798 #1221798 api/uniter/settings: Machine addressability affects how unit settings are updated 5 Low Ian Booth  10 Fix Released
This milestone contains Public information
Everyone can see this information.