Bug #22890: Misleading debug logs when running smart-proxy-openscap-send - OpenSCAP - Foreman

Actions

Copy link

Bug #22890

closed

Misleading debug logs when running smart-proxy-openscap-send

Added by Sanket Jagtap about 6 years ago. Updated about 6 years ago.

Status:

Duplicate

Priority:

Low

Assignee:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Steps:

Stopped the httpd on foreman
Tried to upload the spooled reported from smart-proxy to foreman with smart-proxy-openscap-send

It returns a traceback with misleading logs in proxy.log file
https://paste.fedoraproject.org/paste/K1zrYaIPsZE6ENOqwDEouA


E, [2018-03-13T05:42:28.546310 ] ERROR -- : smart-proxy-openscap-send failed to upload Compliance report for fbdced23-9c08-482a-9186-16fb92827187, generated on 2018-03-13 05:40:58 -0400. Cause: Connection refused - connect(2)
D, [2018-03-13T05:42:28.546390 ] DEBUG -- : Removing directory: /var/spool/foreman-proxy/openscap/arf/fbdced23-9c08-482a-9186-16fb92827187/1/1520934058
D, [2018-03-13T05:42:28.546444 ] DEBUG -- : Removing directory: /var/spool/foreman-proxy/openscap/arf/fbdced23-9c08-482a-9186-16fb92827187/1
D, [2018-03-13T05:42:28.546527 ] DEBUG -- : Removing directory: /var/spool/foreman-proxy/openscap/arf/fbdced23-9c08-482a-9186-16fb92827187

The last two logs are misleading as we still have those directories intact and the report is still not uploaded to foreman as it is still offline.

Related issues 1 (1 open — 0 closed)