Public bug reported:
Now xenial has a juju-mongodb2.6 package that has better support
expectations than our existing (2.4) juju-mongodb package, we should
install and use that by preference for the local provider.
* The juju-local package should depend on juju-mongodb2.6 instead of
juju-mongodb
* On bootstrap, the local provider should try to install juju-mongodb2.6 on
xenial
* The init scripts should look in the 2.6 specific location when starting
mongodb
This doesn't need to include upgrading existing running local providers
to mongo 2.6, but some sane selection needs to happen if both can be
installed.
** Affects: juju-core
Importance: Undecided
Status: Fix Released
** Affects: juju-core/1.25
Importance: High
Status: Triaged
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: local-provider packaging
** Also affects: juju-core
Importance: Undecided
Status: New
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Importance: Undecided => High
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Milestone: None => 1.25.6
** Tags added: local-provider packaging
** Changed in: juju-core
Status: New => 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/1570650
Title:
Use juju-mongodb2.6 for 1.25 on xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
