1175127 - Whitelist mozilla-nightly-updates.s3.amazonaws.com in aus4

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)

Description

[Rail Aliiev [:rail]]

+++ This bug was initially created as a clone of Bug #1173338 +++

Just like in bug 1145186, we need to whitelist mozilla-nighlty-updates.s3.amazonaws.com domain in both production and dev instances of balrog.

Thanks.

Comment 1

[Rail Aliiev [:rail]]

Typo..... it should be mozilla-nightly-updates.s3.amazonaws.com

Sorry about that. :/

Comment 2

[Rail Aliiev [:rail]]

Is there any chance to whitelist the domain today so we don't worry about this next week in Whistler? :)

Comment 3

[Rail Aliiev [:rail]]

ping?

Comment 4

[C. Liang [:cyliang]]

My apologies: my move of this bug in our kanban board marked it as mine right before I went on pre-Whistler PTO, so no one touched it while I was gone. =\

Rail: Can you please verify that the domain is correctly whitelisted for the -dev instance of balrog before I make changes to -prod?

Based on earlier bugs, it's not clear to me if whitelisted domains always must be to be added to both the admin and the balrog config files to work correctly.  I added mozilla-nighlty-updates.s3.amazonaws.com to both.

Comment 5

[Rail Aliiev [:rail]]

No worries, I suspected something like that. ;)

I just tested the whistelisting against the dev instance and it worked fine.

Comment 6

[C. Liang [:cyliang]]

Change pushed out to prod.  Please let me know if if there have been any unintended consequences.

Comment 7

[Rail Aliiev [:rail]]

All green! Thanks a lot.