Closed Bug 1412286 Opened 7 years ago Closed 7 years ago

Download key invalidation not working

Categories

(Socorro :: Symbols, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: peterbe, Assigned: peterbe)

Details

Attachments

(1 file)

Attached file peterbe.zip
Steps to reproduce:

1. Go to localhost:8000/peterbe.pdb/deadbeef123/peterbe.sym (Expect 404)
2. Upload the attached zip
3. Go to localhost:8000/peterbe.pdb/deadbeef123/peterbe.sym (Expect 200, Get 404)
Assignee: nobody → peterbe
Sadly not possible to reproduce locally :(
Ah. Able to reproduce if I actually use AWS S3 and not minio on localhost:9000.

There seems to be a delay between S3 PUT and S3 ListObjectsV2. 
I put some print statements and can assert that the S3 PUT command did happen (successfully) BEFORE the S3 ListObjectsV2 happened, yet the ListObjectsV2 concluded that the file does not exist. 

So we need a way to tell the cache to "wait a little longer" before it concludes that the file doesn't exist.
For the record, I tried switching from ListObjectsV2 to HeadObject (in fact I used both) and HeadObject too says it's not there yet.
Invalid testing. The reason it manifested itself was because the symboldownloader forces the debugID to be uppercase. But I uploaded a fake .zip whose debugID was all hex chars but it was in lowercase. That triggered a mismatch in the "cache key comparisons".
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: