[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.pl... ] Evgheni Dereveanchin reassigned OVIRT-933: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra)

Fix repoproxy service and logging mess --------------------------------------

Key: OVIRT-933 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: Evgheni Dereveanchin Priority: High

There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else.

-- This message was sent by Atlassian JIRA (v1000.620.0#100023)