Bug #24508: Rely on loaded settings when moving corrupted reports from spool - OpenSCAP - Foreman

Actions

Copy link

Bug #24508

closed

Rely on loaded settings when moving corrupted reports from spool

Added by Ondřej Pražák almost 7 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Pražák

Target version:

smart_proxy_openscap 0.6.11

Difficulty:

Triaged:

Bugzilla link:

1332702

Pull request:

https://github.com/theforeman/smart_proxy_openscap/pull/61

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Spool forwarder executed from script cannot rely on Proxy::OpenSCAP::Plugin.settings as these are populated during proxy start. This was fixed in #22511 by loading the settings. When moving the corrupted report, the StorageFS still uses Proxy::OpenSCAP::Plugin.settings.spooldir. We should pass the needed args from SpoolForwarder so that StoreagFS does not try to look them up in uninitialized global context.

Related issues 1 (0 open — 1 closed)