Red Hat Bugzilla – Bug 506693
404 Error when accessing help/contact.pxt
Last modified: 2009-09-10 16:38:04 EDT
Description of problem:
When accessing over WEBUI:
a non existing system:
a non exiting channel:
a non existing probe, ...
we every time get a web page saying "sm. could not be found", "Internal Server Error" or similar that contains a kind of "contact us" link. By following such a link, we receive:
404 Error - File Not Found
Please report this error to your local administrator.
Version-Release number of selected component (if applicable):
(my version: Satellite-5.3.0-RHEL4-re20090612.0)
Steps to Reproduce:
1. Log into the satellite and open
(Make sure you have a non-existing system id in the URL.)
2. You shall see a "We're sorry, but the system could not be found. " web page.
3. Click on the "this form" link in the 3rd point of web page:
"You've found an error in our site. Please help us by filling out this form with details of how you received this message."
You get following web page:
"404 Error - File Not Found
Please report this error to your local administrator."
You shall be redirected to an existing page with expected contents.
this is a hosted leftover, satellite customers have their own support contacts which is why the contact page does not exist.
removed contact link to prevent error.
mass move to onqa
i see...but the grep you have above will return all the links that are posted to hosted as well so it won't be near the 385 occurrences
i see a few left in our string resource files and will also make sure there are none left on the perl logic side.
i found three more occurrences in our java string files and one in a java logic file. the logic file had a string that was actually dead code.
the three in the strings files will not be translated until next release.
commit for above,
OK, I just know it was more than one "page" to fix. Thank you.
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.