Closed
Bug 1100650
Opened 11 years ago
Closed 10 years ago
payment postback errors are not getting reported due to API 404
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kumar, Unassigned)
Details
When Webpay encounters an error, it posts to the Marketplace API but that post is failing due to a 404.
HttpClientError: Client Error 404: https://marketplace.firefox.com/api/v1/webpay/failure/webpay:f29d5e2e-8cbb-4375-b3c8-fc6d276c9232/
http://sentry.mktmon.services.phx1.mozilla.com/mkt/webpay-prod/group/12447/
Stacktrace (most recent call last):
File "celery/task/trace.py", line 228, in trace_task
R = retval = fun(*args, **kwargs)
File "celery/task/trace.py", line 415, in __protected_call__
return self.run(*args, **kwargs)
File "nuggets/celeryutils.py", line 35, in wrapped
return fun(*args, **kw)
File "multidb/pinning.py", line 46, in decorator
return func(*args, **kw)
File "multidb/pinning.py", line 46, in decorator
return func(*args, **kw)
File "webpay/pay/tasks.py", line 297, in payment_notify
_notify(payment_notify, transaction)
File "webpay/pay/tasks.py", line 438, in _notify
notifier_task, task_args, simulated=simulated)
File "webpay/pay/utils.py", line 98, in send_pay_notice
notify_failure(url, trans_id)
File "webpay/pay/utils.py", line 122, in notify_failure
'url': url})
File "curling/lib.py", line 202, in patch
headers=headers, params=kwargs)
File "curling/lib.py", line 304, in _request
content=self._try_to_serialize_error(resp))
Comment 1•11 years ago
|
||
Looks like the URL is expecting an object id, not a uuid.
https://github.com/mozilla/zamboni/blob/master/mkt/webpay/urls.py#L25-L26
The code looks like its doing a lookup based on 'uuid' though, so it is just the URL that's wrong, maybe?
https://github.com/mozilla/zamboni/blob/master/mkt/webpay/views.py#L162
| Reporter | ||
Comment 2•11 years ago
|
||
Yep, looks like just the URL regex is wrong
Updated•11 years ago
|
Assignee: nobody → kumar.mcmillan
Priority: -- → P3
| Reporter | ||
Comment 3•10 years ago
|
||
new Marketplace payments features are on hold while we build out the FxA payments service
Assignee: kumar.mcmillan → nobody
Comment 4•10 years ago
|
||
Based on the recently announced future plans for the Marketplace to remove payments, closing these bugs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•