Upgrade Mongo to 3.4

Bug #1672967 reported by Anastasia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Won't Fix
High
Unassigned

Bug Description

Upgrade to Mongo 3.4 will allow us to:
* stop backporting s390 fix as it comes with s390 support;
* IS is hitting some bugs with Mongo 3.2 that are fixed in Mongo 3.4

This upgrade is highly desirable.

Tags: mongodb
Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Changed in juju:
milestone: 2.3-beta2 → none
Revision history for this message
John A Meinel (jameinel) wrote :

See also https://bugs.launchpad.net/juju/+bug/1760390

we're likely to jump 3.4 and go straight to 3.6 in Bionic.

Changed in juju:
assignee: Michael Hudson-Doyle (mwhudson) → nobody
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

juju is now using mongo 4.0 and 4.4 by default.

Changed in juju:
status: Triaged → Won't Fix
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.