--sslPEMKeyPassword parameter must be passed with = on yakkety
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Michael Hudson-Doyle | ||
juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
juju-mongodb3.2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
yakkety:
root@unembroile
2016-05-
Invalid command: ignored
Options:
General options:
-h [ --help ] show this usage information
[--help output]
xenial:
ubuntu@
2016-05-
2016-05-
2016-05-
[normal startup]
Passing --sslPEMKeyPass
The changes between xenial and yakkety certainly don't *look* like they should cause this: http://
tags: | added: blocker |
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 |
tags: | added: patch |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta7 → none |
milestone: | none → 2.0-beta7 |
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 --sslClusterPas sword, --password (for the shell only) and --verbose. I guess we should tell mongodb?