'juju-db.mongodump' doesn't have apparmor permissions to write log files to $HOME
Bug #1941656 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Committed
|
High
|
Simon Richardson | ||
Bug Description
While trying to obtain a dump of a production database, we had to play tricks with where we were putting the dump file, because the apparmor permissions we supply for juju-db don't allow writing to a user's home directory.
We should fix the apparmor settings even if we want mongod itself to be restricted, it is very hard to use a dump tool that can't write to normal paths.
| Changed in juju: | |
| milestone: | 2.9-next → 3.1-beta1 |
| Changed in juju: | |
| milestone: | 3.1-beta1 → 3.1-rc1 |
Revision history for this message
| Simon Richardson (simonrichardson) wrote | #1 |
| Changed in juju: | |
| assignee: | nobody → Simon Richardson (simonrichardson) |
Revision history for this message
| Simon Richardson (simonrichardson) wrote | #2 |
| Changed in juju: | |
| milestone: | 3.1-rc1 → 3.1-rc2 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
To post a comment you must log in.
Isn't this a case of not having home interface[1] in the plugs section for mongodump[2]?
1. https:/
2. https:/