Payment notification handler fails with 500 error
Bug #656533 reported by
Anthony Lenton
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:/
2010-10-07 14:39:22,125 INFO Notification failed to be sent to url 'https:/
Changed in software-center-agent: | |
importance: | Undecided → Low |
milestone: | none → post-maverick |
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 |
Changed in software-center-agent: | |
milestone: | 4-staging → 5-production |
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.
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): 2010-10- 27/71154- 1761rangpur53. oops
www-oops/
because they are arriving after the subscription has already transitioned past PaymentInitiated.