upgrade juju-mongodb3.2 to 3.2.15

The previous juju-mongodb3.2 version was 3.2.12. 3.2.13 and 3.2.14 contains numerous bug fixes, some of which are important to Juju. Of particular interest are:

https://jira.mongodb.org/browse/SERVER-25318
https://jira.mongodb.org/browse/SERVER-26076
https://jira.mongodb.org/browse/SERVER-26381
https://jira.mongodb.org/browse/SERVER-28548
https://jira.mongodb.org/browse/SERVER-24963
https://jira.mongodb.org/browse/SERVER-28026
https://jira.mongodb.org/browse/SERVER-26452
https://jira.mongodb.org/browse/SERVER-22053

There are also numerous performance related improvements, especially for the WiredTiger storage engine.

This bug was fixed in the package juju-mongodb3.2 - 3.2.15-0ubuntu1

---------------
juju-mongodb3.2 (3.2.15-0ubuntu1) artful; urgency=medium

  * New upstream release. (LP: #1699354)

 -- Michael Hudson-Doyle <email address hidden> Mon, 10 Jul 2017 11:48:35 +1200

Regarding this as covered by the JujuUpdates exception.

Hello Michael, or anyone else affected,

Accepted juju-mongodb3.2 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/juju-mongodb3.2/3.2.15-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Michael, or anyone else affected,

Accepted juju-mongodb3.2 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/juju-mongodb3.2/3.2.15-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Michael, these failed to build on some arches; so looks like they didn't move into proposed (we are always running proposed). Nevertheless, I've installed them now onto our xenial and zesty CI slaves so they will run through the slew of testing now. We'll monitor for regressions.

On 11 August 2017 at 03:22, Nicholas Skaggs <email address hidden>
wrote:

> Michael, these failed to build on some arches; so looks like they didn't
> move into proposed

No... they are in proposed, I promise. They are not in updates yet. that's
what all this is about :)

> (we are always running proposed)

Why would you do that? Do you possibly have proposed and updates mixed up?
Running with updates enabled is always good, running with proposed enabled
is pretty risky.

> . Nevertheless, I've
> installed them now onto our xenial and zesty CI slaves so they will run
> through the slew of testing now. We'll monitor for regressions.

Thanks.

We've been using and testing against this newer version in our CI for more than a month without seeing any issues. All normal juju operations work, and I can connect to the juju database as expected. I tested this on xenial and zesty.

This bug was fixed in the package juju-mongodb3.2 - 3.2.15-0ubuntu1~16.04.1

---------------
juju-mongodb3.2 (3.2.15-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport to Xenial. (LP: #1699354)
  * Drop d/patches/fix-boost-1.62-build.patch.

 -- Michael Hudson-Doyle <email address hidden> Mon, 10 Jul 2017 15:48:40 +1200

The verification of the Stable Release Update for juju-mongodb3.2 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package juju-mongodb3.2 - 3.2.15-0ubuntu1~17.04.1

---------------
juju-mongodb3.2 (3.2.15-0ubuntu1~17.04.1) zesty; urgency=medium

  * Backport to Zesty. (LP: #1699354)

 -- Michael Hudson-Doyle <email address hidden> Mon, 10 Jul 2017 15:48:40 +1200