Sending MOZ_USER_ID to Billing API causes internal error

RESOLVED FIXED in 2013-06-27

Status

P2
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: kumar, Assigned: keir)

Tracking

2013-06-27
x86
Mac OS X
Points:
---

Details

(Whiteboard: [P1 for seahorse])

Per bug 877923 we'd like to pass a new ArrayOfBillingConfigurationOption like this:

MOZ_USER_ID='obfuscated-string'

This causes an internal error in Bango's test system.
Assignee: nobody → keir
This isn't ready on the Bango side yet.  In test tomorrow and live on Thursday.
(Assignee)

Comment 2

5 years ago
This is now on test.
Bango is holding off on landing this on Test until Durango testing stabilizes
Priority: -- → P1
Priority: P1 → P2
Whiteboard: [P1 for seahorse]
this has landed on Bango's test environment. It's not on stage yet.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-06-27
Keir, what are the plans for pushing this to production?
Sending MOZ_USER_ID is still causing a 500 on Bango Test. This is the latest error we received:

Jul 12 08:00:55 localhost6.localdomain: [] s.bango:INFO Received notification for billing_config_id '372590': bango_response_code: 'INTERNAL_ERROR'; bango_response_message: 'A problem on the server meant that the request could not be processed'; bango_trans_id: '0'; moz_transaction: 'webpay:a4b9b219-96da-4b15-a5b1-f6f74c52984b' :/data/www/payments-dev.allizom.org/solitude/lib/bango/resources/notification.py:36
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 7

5 years ago
Just tried this myself - no issue.  Can you retry?
Thanks Keir, it is working for me on Test now
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.