Description of problem: when a user tries to reset their password via the forgot password page they get a 500 error after hitting the "send password" button. How reproducible: go to https://<spacewalk-hostname>/help/forgot_password.pxt attempt to change your password by setting the username and email address then click the "send password" button Actual results: user receives a 500 error the administrators get sent a traceback email The following exception occurred while executing this request: POST /help/forgot_password.pxt HTTP/1.1 (from browser) /help/forgot_password.pxt (from Apache) Error message: RHN::Exception: DBD::Pg::st execute failed: ERROR: can't read "the_log_id": no such variable CONTEXT: can't read "the_log_id": no such variable while executing "return $the_log_id" (procedure "__PLTcl_proc_228922" line 4) invoked from within "__PLTcl_proc_228922" in PL/Tcl function "_get_log_id" PL/pgSQL function "get_log_id" line 6 at assignment PL/pgSQL function "web_contact_log_trig_fun" line 4 at assignment RHN::DB /usr/share/perl5/vendor_perl/RHN/DB.pm 122 RHN::Exception::DB::throw RHN::DB::User /usr/share/perl5/vendor_perl/RHN/DB/User.pm 437 RHN::DB::handle_error Sniglets::Users /usr/share/perl5/vendor_perl/Sniglets/Users.pm 205 RHN::DB::User::commit PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 482 Sniglets::Users::forgot_password_cb PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 103 PXT::ApacheHandler::pxt_parse_data PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 103 (eval) main -e 0 PXT::ApacheHandler::handler main -e 0 (eval) Expected results: an email should be sent to the user with a new random password
it seems as though this function is not able to get a value for the_log_id " create or replace function _get_log_id() returns integer as $$ global the_log_id return $the_log_id $$ language pltclu set search_path from current; " its getting called by the get_log_id function and failing note this is on PostgreQSL 8.4.18 on RHEL 6.5
I confirmed this is fixed in spacewalk 2.1 nightly but its still broken in 2.0
Right, the page was rewritten to java within Bug 1015747. Switching to MODIFIED. I am afraid, we're not going to fix the bug for Spacewalk 2.0.
thats unfortunate but understandable considering 2.1 is planned tentatively to be released in the near future.
Switching MODIFIED Spacewalk bugs to ON_QA before 2.1 release.
Spacewalk 2.1 has been released. https://fedorahosted.org/spacewalk/wiki/ReleaseNotes21