Description of problem: On Spacewalk 1.4 with postgresql backend, I get a 500 HTTP error code on page rhn/schedule/InProgressSystems.do. The traceback is : The following exception occurred while executing this request: GET /network/systems/details/history/event.pxt?sid=1000010001&hid=23 HTTP/1.1 (from browser) /network/systems/details/history/event.pxt (from Apache) Date: Fri Jul 8 12:53:24 2011 Headers: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4 Connection: keep-alive Cookie: __utmz=84819014.1308124805.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=84819014.945858238.1308124805.1308124805.1308124805.1; pxt-session-cookie=352x72ab762c28b8f4e18a0f9e38d77d56d0 Host: tu-spa-d15.cst.cnes.fr Referer: https://srvHostname/rhn/schedule/InProgressSystems.do?aid=23 User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30 Form variables: hid => 23 sid => 1000010001 User Information: User administrator (id 1, org_id 1) Error notes: (none) Initial Request: Yes Error message: RHN::Exception: DBD::Pg::st execute failed: ERROR: column "package" does not exist at character 623 RHN::DB /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB.pm 228 RHN::Exception::DB::throw RHN::DB::st /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB.pm 564 RHN::DB::handle_error RHN::DB::DataSource /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB/DataSource.pm 75 RHN::DB::st::execute_h RHN::DataSource /usr/lib/perl5/vendor_perl/5.8.8/RHN/DataSource.pm 108 RHN::DB::DataSource::run_query RHN::DB::Server /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB/Server.pm 1038 RHN::DataSource::execute_query RHN::DB::Server /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB/Server.pm 1096 RHN::DB::Server::server_event_package_dep_errors RHN::DB::Server /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB/Server.pm 1250 RHN::DB::Server::server_event_package_action RHN::Server /usr/lib/perl5/vendor_perl/5.8.8/RHN/Server.pm 49 RHN::DB::Server::server_event_details Sniglets::Servers /usr/lib/perl5/vendor_perl/5.8.8/Sniglets/Servers.pm 593 RHN::Server::lookup_server_event PXT::Parser /usr/lib/perl5/vendor_perl/5.8.8/PXT/Parser.pm 160 Sniglets::Servers::server_history_event_details PXT::Parser /usr/lib/perl5/vendor_perl/5.8.8/PXT/Parser.pm 72 PXT::Parser::expand_tag PXT::ApacheHandler /usr/lib/perl5/vendor_perl/5.8.8/PXT/ApacheHandler.pm 524 PXT::Parser::expand_tags PXT::ApacheHandler /usr/lib/perl5/vendor_perl/5.8.8/PXT/ApacheHandler.pm 117 PXT::ApacheHandler::pxt_parse_data PXT::ApacheHandler /usr/lib/perl5/vendor_perl/5.8.8/PXT/ApacheHandler.pm 117 (eval) main -e 0 PXT::ApacheHandler::handler main -e 0 (eval) Version-Release number of selected component (if applicable): 1. 4 How reproducible: after scheduling a package removal, go to "Schedule --> In progress system --> Name of the server the action was planned". Steps to Reproduce: 1. 2. 3. Actual results: HTTP 500 error code Expected results: Additional info:
From a traceback I would blame package_removal_failures query. Alas I cannot reproduce it on a fresh Spacewalk nightly.
Aligning under space16.
You can close this bug, it is corrected in spacewalk 1.5
Closing as per comment 3. Thank You, Pierre.