Description of problem: There are issues in the API documentation for ABRT caused by syntax error in Java Doc. Version-Release number of selected component (if applicable): spacewalk-java-1.9.83-46 How reproducible: Always Steps to Reproduce: 1. Help -> API -> Overview -> system.crash https://xxxxx.redhat.com/rhn/apidoc/handlers/CrashHandler.jsp 2. API call getCrashOverview https://xxxxx.redhat.com/rhn/apidoc/handlers/CrashHandler.jsp#getCrashOverview or API call getCrashesByUuid https://xxxx.redhat.com/rhn/apidoc/handlers/CrashHandler.jsp#getCrashesByUuid Actual results: API documentation is broken -> #prop_des Method: getCrashOverview Description: Get Software Crash Overview Parameters: string sessionKey Returns: array: struct - crash string "uuid" - Crash UUID string "component" - Package component (set if unique and non empty) int "crash_count" - Number of crashes occurred #prop_des("int", "system_count", "Number of systems affected") dateTime.iso8601 "last_report" - Last crash occurence Method: getCrashesByUuid Description: List software crashes with given UUID Parameters: string sessionKey string uuid Returns: array: struct - crash int "server_id" - ID of the server the crash occurred on #prop_des("string", "server_name", "Name of the server the crash occured on") int "crash_id" - ID of the crash with given UUID int "crash_count" - Number of times the crash with given UUID occurred string "crash_component" - Crash component dateTime.iso8601 "last_report" - Last crash occurence Expected results: API documentation is correct. No '#prop_des' strings. Additional info:
Fixed in Spacewalk master: aff95b6fa6ab2699f4940e9153df8e6694d4e580
Satellite 5.6 has been released. This bug was tracked under the release. This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly before release). Moving to CLOSED CURRENT_RELEASE. Text from Upgrade Erratum follows: 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. http://rhn.redhat.com/errata/RHEA-2013-1395.html