"juju backups" shows no backup, yet the "backup" mongodb database is 20GB big
Bug #1789840 reported by
Junien F
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Hi,
The following is happening on a 2.3.8 controller :
$ juju backups
No backups to display.
Yet, on mongo :
juju:PRIMARY> show databases
[...]
backups 23.559GB
The space is in the "backups.chunks" collection, as expected :
backups.
Also :
juju:PRIMARY> db.backups.
{
"_id" : ObjectId(
"chunkSize" : 261120,
"length" : NumberLong(
"md5" : "b7eab51f190185
"filename" : "<uuid>"
}
How can we get rid of this ?
Thanks
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: backup-restore |
To post a comment you must log in.
This feels like something started creating backup files, and then we removed the *reference* to the backups, but didn't actually remove the backup content.