Description of problem: Ref: https://openshift.redhat.com/community/forums/openshift/cannot-show-my-applications-page#comment-27700 From User: Login to OpenShift and click MY APPS link but the following error is displayed. We appear to be having technical difficulties It seems there is no ref#, I just attached the error page screenshot. I'm logging in using my account and just clicked "MY APPS" link from top page, in this case, the error page shows "SIGN IN" link at right top, but when I click "MY ACCOUNT" link from top page, I can see my account detail. FYI, https://openshift.redhat.com/app/console/applications/qwassr -> shows error message like my applications page https://openshift.redhat.com/app/console/applications/test -> works https://openshift.redhat.com/app/console/applications/silk -> works Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 701402 [details] openshift error screenshot - no ref id
Created attachment 701403 [details] curl rest api output curl -i -u kimitake:<password> https://openshift.redhat.com/broker/rest/domains/kimitakeblog/applications > output.txt
The user has: "embedded":{"10gen-mms-agent-0.1":{"info":{}} in one of their apps which is causing ActiveResource to try to generate a class called 10genmmsagent01. Should they be receiving this?
Clayton: I checked with the user and here is his feedback: I have followed the page[1] and installed 10gen mms agent, and it seems to work well. I installed it at least one month ago and I could access my apps page after that. Why I get the issue recently? [1] https://access.redhat.com/knowledge/docs/en-US/OpenShift/2.0/html/User_Guide/chap-OpenShift-User_Guide-Application_Maintenance_Monitoring_and_Troubleshooting.html#sect-User_Guide-Monitoring_Applications_with_the_MongoDB_Monitoring_Service_MMS
*** This bug has been marked as a duplicate of bug 912789 ***
Fixed on master. Scheduled to be fixed in production in the next deploy (Monday, March 11th).