Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1542023

Summary: Cannot send Arf reports from spool
Product: Red Hat Satellite Reporter: Ondřej Pražák <oprazak>
Component: SCAP PluginAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Sanket Jagtap <sjagtap>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: hyu, mhulan, oprazak, sjagtap
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:12:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1624072    
Bug Blocks: 1332702    

Description Ondřej Pražák 2018-02-05 12:13:36 UTC
Description of problem:
Reports in spool cannot be sent to the server, running smart-proxy-openscap-send has no effect.

Version-Release number of selected component (if applicable):
6.3.0

How reproducible:
Always

Steps to Reproduce:
1. Make sure you have a report in spool on proxy
2. run smart-proxy-openscap-send

Actual results:
No report is uploaded to Sat server, the report remains in spool on proxy

Expected results:
Report is uploaded and removed from spool.

Additional info:

Comment 1 Ondřej Pražák 2018-02-05 12:15:20 UTC
Created redmine issue http://projects.theforeman.org/issues/22511 from this bug

Comment 3 Satellite Program 2018-02-05 13:06:56 UTC
Upstream bug assigned to oprazak

Comment 4 Satellite Program 2018-02-05 13:06:59 UTC
Upstream bug assigned to oprazak

Comment 6 Satellite Program 2018-03-16 14:06:24 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22511 has been resolved.

Comment 7 Sanket Jagtap 2018-09-19 09:52:00 UTC
Build: Satellite 6.4.0 snap 22


1) Provisioned a Host with scap from External Capsule 
2) Stopped the httpd on satellite.
3) Ran foreman_scap_client on client
4) Report present in Capsule spool dir /var/spool/foreman-proxy/openscap
5) Started the httpd on satellite
6) Ran smart-proxy-openscap-send on Capsule to send the report to Satellite

Report is successfully uploaded to Satellite by running smart-proxy-openscap-send

Comment 8 Ondřej Pražák 2018-10-02 08:16:59 UTC
*** Bug 1634223 has been marked as a duplicate of this bug. ***

Comment 9 Bryan Kearney 2018-10-16 19:12:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927