1149539 - Deploy Splice 1.1.5 with deployment cache bug fixed to Staging

Status: RESOLVED FIXED

(Content Services Graveyard :: Tiles: Ops, defect)

Description

[Olivier Yiptong [:oyiptong]]

This release fixes the bug where the tile index file read by onyx is not updated.

Ways to test:

1. publish tiles with deploy option (no scheduling)
2. note the tiles served by onyx
3. publish a different set of tiles, again with deploy option (no scheduling)
4. note that the tiles served by onyx have changed

Comment 1

[Daniel Thorn [:relud]]

I've triggered a build, it should reach staging in the next 15 minutes.

Comment 2

[Daniel Thorn [:relud]]

build failed due to rpm mirror issues. re-initiated and it's in staging now.

Comment 3

[Ed Lee :Mardak]

I was able to upload tiles and see it change from some empty object {} at https://onyx_tiles.stage.mozaws.net/v2/links/fetch/en-US

to the current redirect that shows the tiles I uploaded.

However, the splice UI shows:  Error: 504 

I'll test by uploading a different set of tiles to make sure 1.1.5 caching is fixed.

Comment 4

[Ed Lee :Mardak]

I uploaded a new set of tiles, and https://onyx_tiles.stage.mozaws.net/v2/links/fetch/en-US redirects to the new json.

splice UI also showed successful output instead of 504:

    https://tiles-resources-stage-tiless3-j2bbpjdfjb7t.s3.amazonaws.com/desktop/US/en-US.fe4a893f70b26e98d5fdb203de8698a95327494b.json,true
    https://tiles-resources-stage-tiless3-j2bbpjdfjb7t.s3.amazonaws.com/desktop_tile_index.json,true
    https://tiles-resources-stage-tiless3-j2bbpjdfjb7t.s3.amazonaws.com/distributions/desktop/924f53ddd38f0b648af00f0f8f0c1bcd33aa8cc6.2015-03-31T19-07-13.119135.json,true