FWIW, passing --sslPEMKeyPassword=ignored also works to run mongo for
the juju test suite on Arch Linux. FWIW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-mongodb3.2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
** Project changed: juju-core => juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword parameter must be passed with = on yakkety
To manage notifications about this
It turns out that upstream had also run into this, so we could also fix
this in the juju-mongodb3.2 package by cherry-picking this change:
https://github.com/mongodb/mongo/commit/b766d1a46bacf5ff94c585543e0e6538da559633
--
You received this bug notification because you are a member of Ubuntu
** Changed in: juju-core
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/1581284
Title:
--sslPEMKeyPassword parameter must be passed with = on yakkety
To
PR: https://github.com/juju/juju/pull/5389
** Changed in: juju-core
Status: In Progress => 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/1581284
Title:
--sslPEMKeyPassword
This bug was fixed in the package juju-core - 2.0~beta6-0ubuntu2.16.10.2
---
juju-core (2.0~beta6-0ubuntu2.16.10.2) yakkety; urgency=medium
* Add patch to fix up mongo arguments to fix autopkgtest on yakkety.
(LP: #1581284)
-- Michael Hudson-Doyle
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword parameter must be passed with = on yakkety
To manage notifications about this bug go to:
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => Critical
** Changed in: juju-core
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: juju-core
Milestone: None => 2.0-beta7
** Changed in: juju-core
Attaching the debdiff I'm about to upload.
** Patch added:
"juju-core-2.0~beta6_2.0~beta6-0ubuntu2.16.10.1_2.0~beta6-0ubuntu2.16.10.2.diff"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword parameter must be passed with = on yakkety
To manage notifications about this bug go to:
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags added: blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword parameter
I'm like 90% sure that it's this change in the boost 1.59 changelog:
"Stop options with implicit value from consuming separate tokens"
It will also affect --sslClusterPassword, --password (for the shell
only) and --verbose. I guess we should tell mongodb?
** Also affects: juju-core
Dead easy to work around in juju though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581284
Title:
--sslPEMKeyPassword parameter must be passed with = on yakkety
To manage notifications about
14 matches
Mail list logo