Closed Bug 722716 Opened 13 years ago Closed 13 years ago

Can't log into FlightDeck dev

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

x86_64
Windows 7
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: zcampbell, Assigned: oremj)

Details

(Whiteboard: [dev][fromAutomation])

I can't log into Flight Deck dev using the automation account. The traceback reads: Traceback (most recent call last): File "/data/www/builder-addons-dev.allizom.org/flightdeck/vendor/lib/python/django/core/handlers/base.py", line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/person/views.py", line 156, in browserid_login assertion=request.POST['assertion']) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/person/views.py", line 123, in browserid_authenticate amouser = AMOAuthentication.auth_browserid_authenticate(email) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/amo/authentication.py", line 114, in auth_browserid_authenticate return AMOAuthentication.fetch_amo_user(email) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/amo/authentication.py", line 120, in fetch_amo_user auth_cursor = get_amo_cursor() File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/amo/helpers.py", line 32, in get_amo_cursor db=settings.AUTH_DATABASE['NAME']) File "/usr/lib64/python2.6/site-packages/MySQLdb/__init__.py", line 81, in Connect return Connection(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 187, in __init__ super(Connection, self).__init__(*args, **kwargs2) OperationalError: (1044, "Access denied for user 'addons_dev'@'10.8.70.20_' to database 'addons_dev'")
Assignee: nobody → server-ops
Component: Add-on Builder → Server Operations: Web Operations
Product: addons.mozilla.org → mozilla.org
QA Contact: add-on-builder → cshields
Version: 0.9 → other
Assignee: server-ops → oremj
This should be fixed. We refreshed the addons_dev database and I updated the builder-dev configs, but forgot to push out that change.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Zac, this is fixed now, right? (Looks like it from automation.)
Yes verified fixed.
Status: RESOLVED → VERIFIED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.