Description of problem: Since "Bug 386691 - Need unattended way to run sosreport" sosreport should be able to run non-interactively. But when diagnose method finds any problem, it asks the user whether to continue. And ends with traceback because it can't get any answer. Version-Release number of selected component (if applicable): sos-1.7-9.2.el5_2.2.noarch How reproducible: 100% Steps to Reproduce: 1. trigger any diagnose method in any plug-in during sosreport run Actual results: traceback when run unattended: http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=5490009 Expected results: No traceback, graceful exit. Additional info:
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Although sosreport is designed to run unattended if required to do so, recent versions still prompted users for input during diagnose method tests if the test found any problem. This prompt meant that sosreport was unable to run unattended. Furthermore, when it did not receive a reply to the prompt, sosreport would crash. Sosreport now automatically chooses the option to continue instead of prompting the user whether to continue or not, and can therefore run unattended.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1418.html