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.
Created attachment 1459638[details]
Screenshot of error on UI
Description of problem:
Version-Release number of selected component (if applicable):
Build:Satellite 6.4 snap 12
How reproducible:
Always
Steps to Reproduce:
1. On Satellite 6.3.2 Configure host with OSCAP and have arf-reports generated and present in satellite
2. Perform Upgrade from 6.3 to 6.4.0 snap 12 , using documented steps
3. Visit those reports generated before upgrade , VIew Full report , or try to download those report
Actual results:
PFA
Expected results:
Full report should be generated
Additional info:
Production and proxy log PFA
I guess you have both Satellite and Capsule upgraded. I don't recall any changes in storage of arf reports, could you please check that you can download that report on your 6.3 instance before upgrade? Is this the path?
/var/lib/foreman-proxy/openscap/reports/arf/6cbb3fb5-b201-42cf-9813-1c233ce54955/7623/1531826160/9871f8e6fa1f4609b9b5a8fa79587efcd875629edf5b7afdee5f55b18f33e213
Is this file removed as part of upgrade?
I re-tested this, but this time it was not reproducible and the reports were intact. But yes, we can handle the exception.
Removing the blocker flag as it's not reproducible
Build: Satellite 6.4.0 snap 21
Now we get a Error message without traceback if , the arf file is missing on the satellite
ERF12-1831 [ProxyAPI::ProxyException]: Unable to get HTML version of requested report from Capsule ([RestClient::InternalServerError]: 500 Internal Server Error) for Capsule https://sat-host:9090/compliance/
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
Created attachment 1459638 [details] Screenshot of error on UI Description of problem: Version-Release number of selected component (if applicable): Build:Satellite 6.4 snap 12 How reproducible: Always Steps to Reproduce: 1. On Satellite 6.3.2 Configure host with OSCAP and have arf-reports generated and present in satellite 2. Perform Upgrade from 6.3 to 6.4.0 snap 12 , using documented steps 3. Visit those reports generated before upgrade , VIew Full report , or try to download those report Actual results: PFA Expected results: Full report should be generated Additional info: Production and proxy log PFA