action #32635
closedWorker cannot create /var/lib/openqa/cache directory
0%
Description
This situation happens when worker is using caching and only openQA-worker is installed
Mar 01 18:40:36 openqaworker12 worker[23629]: mkdir /var/lib/openqa/cache: Permission denied at /usr/share/openqa/script/../lib/OpenQA/Worker.pm line 96.
entrance level issue
Updated by coolo about 6 years ago
- Status changed from New to Feedback
That's why openQA-worker has /var/lib/openqa/cache packaged. IMO this is INVALID
Updated by EDiGiacinto about 6 years ago
Sorry, i have to disagree here: from a QA perspective usually you don't want to package caches directory, nor files. They should be considered as temporary directories/files from the application and being created when necessary at runtime. We should instead move the cache dir away from /var/lib, rationale in [1] [2]
1: http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION
2: http://www.pathname.com/fhs/pub/fhs-2.3.html#VARCACHEAPPLICATIONCACHEDATA
Updated by coolo about 6 years ago
"An application (or a group of inter-related applications) must use a subdirectory of /var/lib for its data" - and the assets downloads have to be on the same partition than the pool, so don't bother me with FHS politics. And it's unrelated anyway
Updated by EDiGiacinto about 6 years ago
coolo wrote:
"An application (or a group of inter-related applications) must use a subdirectory of /var/lib for its data" - and the assets downloads have to be on the same partition than the pool, so don't bother me with FHS politics. And it's unrelated anyway
But qcows aren't application data - imo, what you are describing is a different problem
Updated by coolo about 6 years ago
- Status changed from Feedback to Rejected
ok, that derailed quickly. So let's close it - the cache directory is not supposed to be created by worker process, but is packaged