Bug #11905
closed
foreman_openscap needs /openscap dir in order to serve scap policies
Description
In order for foreman_openscap to serve policy files to clients it needs /openscap/ dir in root and appropriate permissions. This doesn't look to be configurable and, also, is not created at install time.
Because of this, running foreman_scap_client throws those errors on the proxy side:
E, [2015-09-21T13:43:57.244321 #30911] ERROR -- : No permission to create directory openscap/content/4
E, [2015-09-21T13:43:57.244506 #30911] ERROR -- : Error occurred: Permission denied - openscap
10.220.50.190 - - [21/Sep/2015 13:43:57] "GET /compliance/policies/4/content HTTP/1.1" 500 44 0.0010
Also, the documentation says: "At the moment, Foreman infrastructure is not able to serve a file to the clients." Which doesn't seem to be true?
Updated by Dominic Cleal over 9 years ago
- Project changed from Foreman to 36
- Category deleted (
Smart Proxy)
Updated by Marek Hulán over 8 years ago
- Project changed from 36 to OpenSCAP
- Triaged set to No
Updated by Ondřej Pražák over 8 years ago
Where scap content files are stored on the proxy is configurable through :contentdir setting and a corresponding directory is created on the first use (in versions 0.6 and 0.5.x). When the path is not writable, the request ends with 500 and a logged error:
ERROR -- : Error occurred: Permission denied @ dir_s_mkdir - /root/scap_files
I think the main issue is fixed already, closing. Feel free to reopen if I am mistaken.