Red Hat Bugzilla – Bug 820842
Incorrect links for JBoss and MongoDB link in help page.
Last modified: 2015-05-14 21:10:08 EDT
Description of problem:
When I click the "JBoss" link on app/console/help page, it will redirect to community/page/jboss-resources page, and this page will return message "The requested page could not be found."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Go to openshift website and login
2.Go to app/console/help page
3.Click the "JBoss" link in the "Troubleshoot" section.
jboss-resources page can not be found on community.
The jboss-resource page should be available.
Not the page does not exist, just wrong links
JBOSS and MongoDB links in app/console/help page are now linked to https://stg.openshift.redhat.com/community/page/jboss-resources and
But the actual ones in stage are :
Only JBOSS link is broken in stage
The 2 links in are now linked to
But the actual pages in prod are :
We have redirects in place for these old urls. The redirects are in the production database and have been fixed. They will be copied back to devenv and staging early next sprint. This should be verified on prod only (as long as the links in the devenv are correct).
Verified this on prod, the 2 links below
are now redirected to developers/mongodb and developers/jboss
This issue happens again on devenv_1808, the jboss page and mongodb page can not be found.
The url of jboss link on help page will redirect to "https://openshifttest.redhat.com/community//community/developers/jboss".
The url of mongodb link on help page will redirect to
Tried this on stage again ,the jboss page still can not be found.
Tested this issue on devenv_1809, it has been fixed now, thanks.
Tested on stage today, the issue happened again.
The above links will return "The requested page could not be found." error.
(In reply to comment #8)
> Tested on stage today, the issue happened again.
> The above links will return "The requested page could not be found." error.
The above 2 links work in prod, reduce the severity.
Tested this issue on devenv_1861, it does not exist now.