Description of problem: Recent nightly version of Spacewalk system management solution issues a Tomcat traceback (Internal Server Error) when trying to view XCCDF scan results (further detailed information) post performing OpenSCAP scan having: --profile=common or --profile=common --cpe=/usr/share/xml/scap/ssg/ssg-fedora-cpe-dictionary.xml in the "Command-line Arguments:" field of the "Schedule New XCCDF Scan" screen. Version-Release number of selected component (if applicable): Spacewalk release 2.1 nightly (spacewalk-setup-2.1.8-1.fc19.noarch.rpm when used with PostgreSQL) How reproducible: Always Steps to Reproduce: 1. Create custom channel, activation_key, register system to that channel 2. Upload / rhnpush SCAP content rpm (created via scap-workbench) to that channel 3. Install the ssg-fedora-xccdf-1-1.noarch.rpm (can attach it to this bugzilla later in case of need) for the registered client 4. Schedule new XCCDF scan having: "Command-line Arguments: --profile=common" or "Command-line Arguments: --profile=common --cpe=/usr/share/xml/scap/ssg/ssg-fedora-cpe-dictionary.xml" and "Path to XCCDF document: /usr/share/xml/scap/ssg-fedora-xccdf/ssg-fedora-xccdf.xml" <-- this file comes from ssg-fedora-xccdf-1-1.noarch.rpm RPM package generated by scap-workbench. 5. Click "Schedule" && "Confirm" SCAP scan 6. Wait for the scan to finish 7. Select particular XCCDF scan run-id, and click "Audit" link (either in "menu-line" or by clicking on the system and then selecting "Audit" sub-tab). Actual results: Spacewalk displays ISE with attached traceback. Expected results: No internal server error / no tomcat traceback. Relevant SCAP scan result files provided as links (after clicking them further information is available). Additional info: See the attached Tomcat catalina output (shortened to mention only relevant information, since the remaining repeated itself). If the particular ssg-fedora-xccdf-1-1.noarch.rpm RPM package is required to be attached here too, let me know (wasn't special, default scap-security-guide Fedora-19 workbench saved as RPM) and re-used as described above. Note: The underlying Spacewalk instance was installed according to guidance from: https://fedorahosted.org/spacewalk/wiki/HowToInstall (with the nightly option being used)
Jan, thanks for report! May I please bring this bug public? I fail to see which part of this bug report is sensitive.
This bug was introduced by spacewalk.git 38c64438926d59eef41d1b8b0ef8c915231bb27e Sadly, the documentation of said patch is rather sparse.
(In reply to Šimon Lukašík from comment #2) > Jan, thanks for report! May I please bring this bug public? > I fail to see which part of this bug report is sensitive. Nothing sensitive here (AFAICS). Just made it private first to double-check. But feel free to go ahead. Thanks for looking at this!
spacewalk.git e44ce3c3af971dace97de1c397540a5e0c9245af Notes for testers: * The regression affected the following two pages: * rhn/systems/details/audit/XccdfDetails.do * rhn/systems/details/audit/ListScap.do * The simplest reproducer: * Have two comparable scans finished (where comparable means scans of the same machine for the same benchmark/profile).
Spacewalk 2.1 has been released. https://fedorahosted.org/spacewalk/wiki/ReleaseNotes21