Bug 1688743
Summary: | OpenSCAP scan history item point to non-existent/wrong detailed result for the scan | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Radovan Drazny <rdrazny> |
Component: | WebUI | Assignee: | Michael Mráka <mmraka> |
Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 580 | CC: | mmraka, rbouikila, tlestach |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spacewalk-java-2.5.14-131-sat | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-19 18:11:14 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: |
Description
Radovan Drazny
2019-03-14 10:58:24 UTC
Reproducer update: 4. schedule some tests on both hosts 5. schedule tests which will fail, e.g. use /noteexist as a path to xccdf file. 6. schedule working tests on both hosts again 7. go to <System Details> -> Audit -> List Scans and notice test xids (when you hover over the links with test names) 8. go to <System Details> -> Events -> History page 9. open the OpenSCAP event details, check test xids whe you hover over "View detailed results" 10. (try to) open "View detailed results" link Fixed in upstream spacewalk git by commit 83c460b061589ef67c9a10b5dcc7374253ad9c8a 1688743 - don't mix scapActionDetail and xccdfTestResult ids Backported to SATELLITE-5.8 as commit 1b836475a7935c52124323986c26a90904b73993 1688743 - don't mix scapActionDetail and xccdfTestResult ids I have tested the basic scenario - schedule two separate OSCAP scans on two clients, let them run, check their results both in Audit tab and in History (of scheduled actions) tab. Both scenarios work now, even for the updated reproducer from comment #1. Problem is, the same issue appeared when scheduling OSCAP scan for multiple hosts using the System Manager. The symptoms are very similar - links to scan results are correct on the Audit tab, but if you go into History tab, you will get an "We're sorry, but the XCCDF scan could not be found." error on all systems included in the scan except one. It seems all hosts included in the scan get the same "&xid=XX" link to a scan report in the History tab, while the id is valid only for one host (probably the one that finished the scan first). This id is actually different for each host. FailedQA Fixed in upstream spacewalk git by commit 0c353993bb0a6e98dc4ed77efe8065f689171f8c 1688743 - find proper result detail for a given server Backported to SATELLITE-5.8 commit dbadfbb27f4b1acfa749ebbc43aff03d8e5bc571 1688743 - find proper result detail for a given server Tested on spacewalk-java-2.5.14-131. As stated in the comment #5, the basic scenario works. Checking the results produced by OSCAP scans scheduled by the System Manager now works as well - logs are available for all hosts included in the scan. VERIFIED 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/RHBA-2019:1551 *** Bug 1686599 has been marked as a duplicate of this bug. *** |