SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial

Bug #1673652 reported by Anastasia
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-mongodb3.2 (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Michael Hudson-Doyle
Yakkety
Fix Released
Undecided
Michael Hudson-Doyle

Bug Description

juju-mongodb 3.2.12-0ubuntu1 is in zesty. It provides several
performance and stability fixes. It also allows us to drop patches to
support rare architectures.

[SRU Information]

juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.

[Impact]

This will affect juju only, juju controllers specifically.

Biggest impact bug that requires new microversion: https://bugs.launchpad.net/juju/+bug/1670891

[QA/Testing]

Juju QA will verify that new controllers work with the new mongo on
all archs for both yakkety and xenial. Existing controller will be
upgraded to the new version and verified. This will be tested both in
Juju CI and manually.

Changed in juju-mongodb3.2 (Ubuntu Xenial):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in juju-mongodb3.2 (Ubuntu Yakkety):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in juju-mongodb3.2 (Ubuntu):
status: New → Fix Released
Changed in juju-mongodb3.2 (Ubuntu Xenial):
status: New → In Progress
Changed in juju-mongodb3.2 (Ubuntu Yakkety):
status: New → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Anastasia, or anyone else affected,

Accepted juju-mongodb3.2 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/juju-mongodb3.2/3.2.12-0ubuntu1~16.10 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

Changed in juju-mongodb3.2 (Ubuntu Yakkety):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in juju-mongodb3.2 (Ubuntu Xenial):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Anastasia, 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.12-0ubuntu1~16.04 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

Revision history for this message
Christopher Lee (veebers) wrote :

Hi Brian, Team,

We've been running some tests using the SRU (3.2.12-0ubuntu1~16.04) version of juju-mongodb and are happy with the results (nothing but passing tests :-) ).

We tested things that had an lxd component as we had control over being able to use proposed (juju itself cannot do that yet).

We tested:
  - Unit tests (http://juju-ci.vapour.ws/job/run-unit-tests-xenial-amd64-mongodb-sru/)
  - Model Migration (http://juju-ci.vapour.ws/job/functional-model-migration-sru/)
  - Deploy (http://juju-ci.vapour.ws/job/lxd-deploy-xenial-amd64-sru/)
  - HA Recovery (http://juju-ci.vapour.ws:8080/job/functional-ha-recovery-sru/)

tags: added: verification-done-xenial verification-done-yakkety
removed: verification-needed
tags: added: verification-done
Revision history for this message
Robie Basak (racb) wrote :

Thank you for detailing the testing you did in comment 3. Based on this it looks fine to release 3.2.12-0ubuntu1~16.04 to xenial-updates.

@Anastasia

I see no claim that the package in yakkety-proposed was tested, so I think verification-done-yakkety is incorrect.

tags: added: verification-needed
removed: verification-done verification-done-yakkety
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-mongodb3.2 - 3.2.12-0ubuntu1~16.04

---------------
juju-mongodb3.2 (3.2.12-0ubuntu1~16.04) xenial; urgency=medium

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

 -- Michael Hudson-Doyle <email address hidden> Thu, 16 Mar 2017 20:13:57 +1300

Changed in juju-mongodb3.2 (Ubuntu Xenial):
status: Fix Committed → Fix Released
tags: added: verification-done-yakkety
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-mongodb3.2 - 3.2.12-0ubuntu1~16.10

---------------
juju-mongodb3.2 (3.2.12-0ubuntu1~16.10) yakkety; urgency=medium

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

 -- Michael Hudson-Doyle <email address hidden> Thu, 16 Mar 2017 20:13:57 +1300

Changed in juju-mongodb3.2 (Ubuntu Yakkety):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.