Incorrect permissions logic in snap wrapper
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
prometheus-snap |
Fix Committed
|
High
|
James Simpson |
Bug Description
On restarting the Prometheus snap, you'll be treated to a lovely spew of "Operation not permitted" errors. For example:
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
Oct 13 01:22:18 juju-dd628a-
There are two issues here:
1) We aren't catering for a scenario where we need to modify permissions once ownership is already altered.
2) We're being overzealous with the permissions being applied. The intention was to ensure that moving to a rootless daemon didn't prevent the snap from reading any of its own files, and for that intention to be met there's no need for us to modify permissions within the TSDB.
Related branches
- Loïc Gomez: Approve (+1)
- prometheus-snap-developers: Pending requested
-
Diff: 67 lines (+20/-8)1 file modifiedsnap_config_wrapper (+20/-8)
Changed in prometheus-snap: | |
status: | New → In Progress |
assignee: | nobody → James Simpson (jsimpso) |
importance: | Undecided → High |
Fix tested in edge and promoted to candidate