Creating backup from controller on Trusty fails

Bug #1798204 reported by Xav Paice on 2018-10-16
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

Juju 2.4.3, controller running on Trusty.

When I try to create a backup of the controller model:

~$ juju create-backup -m controller
ERROR while creating backup archive: while dumping juju state database: error dumping databases: error executing "/usr/lib/juju/bin/mongodump": ERROR: unrecognised option '--sslAllowInvalidCertificates'; ; Export MongoDB data to BSON files.; ; options:; --help produce help message; -v [ --verbose ] be more verbose (include multiple times; for more verbosity e.g. -vvvvv); --version print the program's version and exit; -h [ --host ] arg mongo host to connect to ( <set ; name>/s1,s2 for sets); --port arg server port. Can also use --host ; hostname:port; --ipv6 enable IPv6 support (disabled by ; default); --ssl use SSL for all connections; -u [ --username ] arg username; -p [ --password ] arg password; --authenticationDatabase arg user source (defaults to dbname); --authenticationMechanism arg (=MONGODB-CR); authentication mechanism; --dbpath arg directly access mongod database files ; in the given path, instead of ; connecting to a mongod server - needs ; to lock the data directory, so cannot ; be used if a mongod is currently ; accessing the same path; --directoryperdb each db is in a separate directly ; (relevant only if dbpath specified); --journal enable journaling (relevant only if ; dbpath specified); -d [ --db ] arg database to use; -c [ --collection ] arg collection to use (some commands); -o [ --out ] arg (=dump) output directory or "-" for stdout; -q [ --query ] arg json query; --oplog Use oplog for point-in-time ; snapshotting; --repair try to recover a crashed database; --forceTableScan force a table scan (do not use ; $snapshot);

Hence, we have no backups of this (production) environment.

Tim Penhey (thumper) wrote :

I'm pretty sure this will be additional flags for backup being passed to an older mongo (probably 2.4 in trusty).

Changed in juju:
importance: Undecided → High
status: New → Triaged
tags: added: backup-restore

yep. Trusty runs mongo 2.4 which doesn't have the same flags as 3.2 on
Xenial.

On Wed, Oct 17, 2018 at 4:40 AM Tim Penhey <email address hidden> wrote:

> I'm pretty sure this will be additional flags for backup being passed to
> an older mongo (probably 2.4 in trusty).
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Tags added: backup-restore
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1798204
>
> Title:
> Creating backup from controller on Trusty fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1798204/+subscriptions
>

Xav Paice (xavpaice) wrote :

Subscribed field-medium as this affects production environments.

Changed in juju:
milestone: none → 2.4.8
Anastasia (anastasia-macmood) wrote :

Removing from a milestone as this work will not be done in 2.4 series.

Changed in juju:
milestone: 2.4.8 → none
Andrea Ieri (aieri) wrote :

This is still happening on 2.7.4 controllers, subscribing field high

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

Other bug subscribers