Bug #30353: Compliance reports are not being uploaded to Foreman. - OpenSCAP - Foreman

Actions

Copy link

Bug #30353

closed

Compliance reports are not being uploaded to Foreman.

Added by Ondřej Pražák almost 5 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Pražák

Target version:

Difficulty:

Triaged:

Bugzilla link:

1854397

Pull request:

https://github.com/theforeman/foreman_openscap/pull/439, https://github.com/theforeman/foreman_openscap/pull/442, https://github.com/theforeman/foreman_openscap/pull/443

Fixed in Releases:

foreman_openscap 3.0.1, foreman_openscap 4.0.1

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1854397

Description of problem:
Compliance reports are not being uploaded to Foreman.

How reproducible:
- Always

Steps to Reproduce:
1. Register a host to Foreman.
2. Assign OpenSCAP proxy, theforeman.foreman_scap_client ansible role and compliance policy to host.
3. Run ansible roles for hosts.

Actual results:
Report not uploaded from proxy to Foreman server, cause: Failed to upload to Foreman, saving in spool. Failed with: 500 "Internal Server Error"

Expected results:
Reports are uploaded to Foreman server.

Additional info:
In /var/log/foreman/production.log:

error (ActiveRecord::RecordNotUnique): PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_scaptimony_asset_policies_on_asset_id_and_policy_id"
DETAIL: Key (asset_id, policy_id)=(2, 3) already exists.

Actions

Copy link

Updated by Ondřej Pražák almost 5 years ago

Subject changed from Compliance reports are not being uploaded to Foreman. to Compliance reports are not being uploaded to Foreman.
Assignee set to Ondřej Pražák

Actions

Copy link