** Changed in: juju
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
[2.0] bump mongod to 3.2.9
To manage notifications about this bug go
** Changed in: juju
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
[2.0] bump mongod to 3.2.9
To manage notifications about this bug go to:
** Changed in: juju
Assignee: (unassigned) => Alexis Bruemmer (alexis-bruemmer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
[2.0] bump mongod to 3.2.9
To manage notifications
This bug was fixed in the package juju-mongodb3.2 - 3.2.9-0ubuntu1~16.04
---
juju-mongodb3.2 (3.2.9-0ubuntu1~16.04) xenial; urgency=medium
* Build for Xenial. (LP: #1605976)
-- Michael Hudson-Doyle Thu, 01 Sep 2016
09:02:51 +1200
** Changed in:
On 16 September 2016 at 01:34, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> @mwhudson, I utilized the tool locally and everything seemed fine. For
> now, bug 1564500 prevents a full CI run until it lands in xenial proper.
>
Oh well.
> I think we should discuss a set of
@mwhudson, I utilized the tool locally and everything seemed fine. For
now, bug 1564500 prevents a full CI run until it lands in xenial proper.
I think we should discuss a set of autopkgtests to help bridge the gap
in the interim.
That said, given 3.2.9 is in yakkety we've not seen any issues in
Am able to upgrade a bootstrapped Juju controller without issues here.
That's only lightweight QA but it's a data point for you.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
Can we get a CI run or at least some kind of qa with the new mongo? The
point of SRU verification is not only to verify that the bug is fixed
but also that nothing new has broken :-) (I tend to forget this too!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Looks good.
/usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.9
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Hello Mark, 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.9-0ubuntu1~16.04 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
On 31 August 2016 at 02:45, Mark Shuttleworth <1605...@bugs.launchpad.net>
wrote:
> Ah, thank you, I thought we had bundled the database in the Juju package
> and didn't realise it needed all the independent machinery to be invoked.
>
> Bring on the snap era :)
>
Yeah.
I do think we should
Ah, thank you, I thought we had bundled the database in the Juju package
and didn't realise it needed all the independent machinery to be invoked.
Bring on the snap era :)
I do think we should track upstream releases of Mongo because they are
essentially free performance and resilience fixes of
This bug was fixed in the package juju-mongodb3.2 - 3.2.9-0ubuntu1
---
juju-mongodb3.2 (3.2.9-0ubuntu1) yakkety; urgency=medium
* New upstream release. (LP: #1605976) (again)
* Drop one part of s390x-support.patch that was included upstream.
-- Michael Hudson-Doyle
And yakkety has had 3.2.8 for a month, but the SRU never happened :(
Uploading 3.2.9 to yakkety now, and assigning the Xenial task to
Nicholas to get the QA done before actually doing the SRU properly this
time.
** Summary changed:
- [2.0] bump mongod to 3.2.8
+ [2.0] bump mongod to 3.2.9
**
14 matches
Mail list logo