swift-storage config-changed hook runs chown on /srv/node
Bug #1676728 reported by
Brad Marshall
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Swift Storage Charm |
Fix Released
|
High
|
Billy Olsen |
Bug Description
On the current swift-storage charm (checked on both released 17.02 and master), it calls the setup_storage() function, which does a chown on /srv/node. On a busy swift system, this can be multiple terabytes and as you can imagine, this takes a very long time to run. As there's a hook running, this blocks any further activity on that unit, as well as the ability to use juju run.
Are there any other options for this rather than running this very expensive operation on every config changed hook run? Is just leaving it in the install hook sufficient?
Changed in charm-swift-storage: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 17.05 |
Changed in charm-swift-storage: | |
milestone: | 17.05 → 17.08 |
tags: | added: backport-potential sts |
Changed in charm-swift-storage: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As an example, on a cloud with 5TB used storage (millions of objects) per node this operation had been running since March 31 without completion.