Ubuntu
juju-mongodb3.2 package

--sslPEMKeyPassword parameter must be passed with = on yakkety

Bug #1581284 reported by Michael Hudson-Doyle
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Michael Hudson-Doyle
Canonical Juju 2.0-beta7
juju-core (Ubuntu)
Fix Released
Undecided
Unassigned
juju-mongodb3.2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

yakkety:

root@unembroiled-grayce:~# /usr/lib/juju/mongo3.2/bin/mongod --dbpath='db' --sslOnNormalPorts --sslPEMKeyFile mongodb.pem --sslPEMKeyPassword ignored
2016-05-13T02:15:06.941+0000 W CONTROL [main] No SSL certificate validation can be performed since no CA file has been provided; please specify an sslCAFile parameter
Invalid command: ignored
Options:

General options:
  -h [ --help ] show this usage information
[--help output]

xenial:

ubuntu@irredeemable-elba:~$ /usr/lib/juju/mongo3.2/bin/mongod --dbpath='db' --sslOnNormalPorts --sslPEMKeyFile mongodb.pem --sslPEMKeyPassword ignored
2016-05-13T02:15:28.728+0000 W CONTROL [main] No SSL certificate validation can be performed since no CA file has been provided; please specify an sslCAFile parameter
2016-05-13T02:15:28.739+0000 I CONTROL [initandlisten] MongoDB starting : pid=873 port=27017 dbpath=db 64-bit host=irredeemable-elba
2016-05-13T02:15:28.739+0000 I CONTROL [initandlisten] db version v3.2.4
[normal startup]

Passing --sslPEMKeyPassword=ignored works on yakkety.

The changes between xenial and yakkety certainly don't *look* like they should cause this: http://paste.ubuntu.com/16384449/ so I guess it's some dependency that's change.

Tags: blocker patch
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

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?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Dead easy to work around in juju though.

Michael Hudson-Doyle (mwhudson)
tags: added: blocker
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Attaching the debdiff I'm about to upload.

Ian Booth (wallyworld)
Changed in juju-core:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Michael Hudson-Doyle (mwhudson)
milestone: none → 2.0-beta7
status: Triaged → In Progress
Ubuntu Foundations Team Bug Bot (crichton)
tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 13 May 2016 15:13:42 +1200

Changed in juju-core (Ubuntu):
status: New → Fix Released
Revision history for this message
Cheryl Jennings (cherylj) wrote :

PR: https://github.com/juju/juju/pull/5389

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

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

Canonical Juju QA Bot (juju-qa-bot)
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta7 → none
milestone: none → 2.0-beta7
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-mongodb3.2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Reed O'Brien (reedobrien) wrote :

FWIW, passing --sslPEMKeyPassword=ignored also works to run mongo for the juju test suite on Arch Linux. FWIW.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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