Bug 817057 - Console 500 - mongo mms agent failure
Summary: Console 500 - mongo mms agent failure
Keywords:
Status: CLOSED DUPLICATE of bug 815698
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-27 14:35 UTC by Mike McGrath
Modified: 2015-05-15 01:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-27 16:24:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike McGrath 2012-04-27 14:35:52 UTC
Description of problem:
A user with the mongo 10gen monitoring client installed is getting this when trying to log in to the console:

"We're sorry , but something went wrong"

Here's what happens in the logs


Started GET "/app/console/applications" for 88.103.96.80 at Fri Apr 27 10:30:02 -0400 2012
[Barista] Copying all javascripts
  Processing by ApplicationsController#index as HTML
[check_credentials] Check login state
  Checking for logout request
  Not a logout request, checking for cookie
  rh_sso cookie = "0|9IBOdxLZacshezeG476OHHwfHt3kyZRpoRU"
  User has an authenticated session
  Session ticket matches current ticket
ticket_verified timestamp has expired, checking ticket: 0|9IBOdxLZacshezeG476OHHwfHt3kyZRpoRU
Response from Streamline took (/wapps/streamline/cloudVerify.html): 203.089 ms
POST Response code = 200
Login required
Completed 500 Internal Server Error in 5840ms

NameError (wrong constant name 10genMmsAgent01):
  app/models/rest_api/base.rb:61:in `const_defined?'
  app/models/rest_api/base.rb:61:in `find_or_create_resource_for'
  app/models/rest_api/base.rb:140:in `load'
  app/models/rest_api/base.rb:159:in `initialize'
  app/models/rest_api/base.rb:466:in `new'
  app/models/rest_api/base.rb:466:in `instantiate_record'
  app/models/rest_api/base.rb:462:in `instantiate_collection'
  app/models/rest_api/base.rb:462:in `collect!'
  app/models/rest_api/base.rb:462:in `instantiate_collection'
  app/models/rest_api/base.rb:451:in `find_every'
  app/models/rest_api/base.rb:297:in `find'
  app/models/domain.rb:15:in `applications'
  app/controllers/applications_controller.rb:77:in `index'



Started GET "/app/console/applications" for 11.11.22.22 at Fri Apr 27 10:30:02 -0400 2012
[Barista] Copying all javascripts
  Processing by ApplicationsController#index as HTML
[check_credentials] Check login state
  Checking for logout request
  Not a logout request, checking for cookie
  rh_sso cookie = "0|9IBOdxLZacshezeG47obfuscatedU"
  User has an authenticated session
  Session ticket matches current ticket
ticket_verified timestamp has expired, checking ticket: 0|9IBOdxLZacshezeG476OHHwfHt3kyZRpoRU
Response from Streamline took (/wapps/streamline/cloudVerify.html): 203.089 ms
POST Response code = 200
Login required
Completed 500 Internal Server Error in 5840ms

NameError (wrong constant name 10genMmsAgent01):
  app/models/rest_api/base.rb:61:in `const_defined?'
  app/models/rest_api/base.rb:61:in `find_or_create_resource_for'
  app/models/rest_api/base.rb:140:in `load'
  app/models/rest_api/base.rb:159:in `initialize'
  app/models/rest_api/base.rb:466:in `new'
  app/models/rest_api/base.rb:466:in `instantiate_record'
  app/models/rest_api/base.rb:462:in `instantiate_collection'
  app/models/rest_api/base.rb:462:in `collect!'
  app/models/rest_api/base.rb:462:in `instantiate_collection'
  app/models/rest_api/base.rb:451:in `find_every'
  app/models/rest_api/base.rb:297:in `find'
  app/models/domain.rb:15:in `applications'
  app/controllers/applications_controller.rb:77:in `index'

Comment 1 Xiaoli Tian 2012-04-27 15:10:13 UTC
Might be similar to bug 815698, if the same bug, maybe fixed after prod is upgraded.

Comment 2 Fabiano Franz 2012-04-27 16:24:24 UTC
It's the same as bug 815698, will get fixed after the next deploy. Marking duplicate.

*** This bug has been marked as a duplicate of bug 815698 ***


Note You need to log in before you can comment on or make changes to this bug.