Payment notification handler fails with 500 error

Bug #656533 reported by Anthony Lenton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Fix Released
Low
Michael Nelson

Bug Description

We've recently seen this come up in the payments logs. Unfortunately no more details to offer for now:

2010-10-07 14:39:22,125 WARNING An unexpected error occurred while requesting 'https://sc.staging.ubuntu.com/subscriptions/payment_notification/2594174f02dfb5876377b8003ddae1a2/CANCELLED/': HTTP Error 500: INTERNAL SERVER ERROR.
2010-10-07 14:39:22,125 INFO Notification failed to be sent to url 'https://sc.staging.ubuntu.com/subscriptions/payment_notification/2594174f02dfb5876377b8003ddae1a2/CANCELLED/'. Error: HTTP Error 500: INTERNAL SERVER ERROR.

Tags: oops
Changed in software-center-agent:
importance: Undecided → Low
milestone: none → post-maverick
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Currently we only handle the payment notifications AUTHORISED/CANCELLED while in the PaymentInitiated state.

We are seeing oopses like (update with web-link when setup):
www-oops/2010-10-27/71154-1761rangpur53.oops

because they are arriving after the subscription has already transitioned past PaymentInitiated.

Changed in software-center-agent:
status: New → Confirmed
tags: added: oops
Changed in software-center-agent:
status: Confirmed → In Progress
assignee: nobody → Michael Nelson (michael.nelson)
Changed in software-center-agent:
milestone: post-maverick → 3-internal-qa
Changed in software-center-agent:
status: In Progress → Fix Committed
Revision history for this message
Dave Morley (davmor2) wrote :

Logs show no error now when payment is captured, so this is now working as expected.

Changed in software-center-agent:
milestone: 3-internal-qa → 4-staging
Changed in software-center-agent:
milestone: 4-staging → 5-production
Dave Morley (davmor2)
Changed in software-center-agent:
milestone: 5-production → 10.11.0
Changed in software-center-agent:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.