555080 - Uploading a new version fails with no indication

Status: RESOLVED DUPLICATE of bug 553523

(addons.mozilla.org Graveyard :: Developer Pages, defect)

Description

[Yair Halevi (Spock)]

User-Agent:       Mozilla/5.0 (Windows; N; Windows NT 5.1; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 3.5.30729)
Build Identifier: 5.8

When I try to upload a new version, after hitting the "Upload File" button, the "Uploading file" indication appears for several seconds (around 15), and then simply disappears, with no error or success message.

This is happening consistently over the last hour (and it's the first I've tried since 5.8 was pushed).


Reproducible: Always

Steps to Reproduce:
1. Create a new version of an addon
2. Upload a file

Actual Results:  
Upload file page returns to the exact same state as it was before clicking "Upload File"

Expected Results:  
The file should be uploaded and the page updated accordingly, or at least, an error message should be displayed.

Digging into the network traffic with Firebug reveals that the POST with the uploaded file returns a 502 Bad Gateway response (which contains somewhere in its text, a message claiming that the request cannot be served due to high volume).

Then, an additional request is sent to https://diag.sitespect.net (via SSL). The certificate for that site seems to be wrong (it is for *.sitespect.com, not sitespect.net), but I'm not sure if this is related to the failure.

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

Hi there - can you please attach Live HTTP Headers as a plain text attachment to this bug?

Comment 2

[Yair Halevi (Spock)]

Attachment: Live HTTP headers of the request and response

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

Hrm; you hit a 502, which is bad.  If you can reproduce at will, we should get someone from IT/OPS to take a look.  Yair, does this happen all the time?

Comment 4

[Yair Halevi (Spock)]

It happened consistently over a certain period, then I stopped trying and tried again 2 hours or so, and it worked. So I can't really reproduce at will, I guess.