Description of problem: During the web-configuration portion of the satellite installation, if the CA Cert passwords that you enter on the SSL configuration page don't match, you get a 500 error. I had to look at the error logs to determine the source of the error. We should be able to check this and show a nice error message, right? Version-Release number of selected component (if applicable): 3.6 How reproducible: Always Steps to Reproduce: 1. See desc Actual results: 500 Expected results: Nice error Additional info: Error message: RHN::Exception: Message text and queue name required - got (, The CA Cert passwords did not match) PXT::Request /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/PXT/Request.pm 77 RHN::Exception::throw Sniglets::SatInstall /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Sniglets/SatInstall.pm 1155 PXT::Request::push_message Sniglets::SatInstall /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Sniglets/SatInstall.pm 112 Sniglets::SatInstall::gen_sat_cert_cb PXT::ApacheHandler /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/PXT/ApacheHandler.pm 611 Sniglets::SatInstall::satinstall_form_cb PXT::ApacheHandler /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/PXT/ApacheHandler.pm 110 PXT::ApacheHandler::pxt_parse_data PXT::ApacheHandler /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/PXT/ApacheHandler.pm 110 (eval) main /dev/null 0 PXT::ApacheHandler::handler main /dev/null 0 (eval)
Fixed in CVS. Test plan: 1) Begin sat 3.6 installation. 2) At the SSL cert configuration page, enter two different passwords You should get a pretty error message, not a 500 error.
mass change to ON_QA from QA push
Fixed
Mass move from PROD_READY to CLOSED:CURRENTRELEASE