Comment 1 for bug 1287147

I'd like to push in juju-core 1.17.6 as an interim point release as it resolves a number of high/critical bugs (some of which are impacting on OpenStack CI testing).

This includes all fixes from:

https://launchpad.net/juju-core/+milestone/1.17.5
https://launchpad.net/juju-core/+milestone/1.17.6

Note: I declined 1.17.5 for trusty upload as it removed support for juju-mongodb - this is now restored in 1.17.6.

Changelog:

juju-core (1.17.6-0ubuntu1) UNRELEASED; urgency=medium

  * New upstream point release, including fixes for:
    - br0 not bought up by cloud-init with MAAS provider (LP: #1271144).
    - ppc64el enablement for juju/lxc (LP: #1273769).
    - juju userdata should not restart networking (LP: #1248283).
    - error detecting hardware characteristics (LP: #1276909).
    - juju instances not including the default security group (LP: #1129720).
    - juju bootstrap does not honor https_proxy (LP: #1240260).
  * d/control,rules: Drop BD on bash-completion, install bash-completion
    direct from upstream source code.
  * d/rules: Set HOME prior to generating man pages.
  * d/control: Drop alternative dependency on mongodb-server; juju now only
    works on trusty with juju-mongodb.

Testing:
Verified local provider usage on 14.04
Verified MAAS provider on 14.04 deploying 14.04
Verified OpenStack provider on 14.04 deploying 14.04

I specifically confirmed that the juju-mongodb package is being used in all of these test cases.

Note that upstream also do CI against all providers prior to release.

Build log: see attached.