967239 - update tuxedo (+vendor lib) on production

Status: VERIFIED FIXED

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

Description

[Robert Helmer [:rhelmer]]

Tuxedo has been updated and tested on stage, we'd like to make these changes live on production. The commit is: https://github.com/mozilla/tuxedo/commit/598b9eeafa1e08b044f60d88ded7aa917e24e38b

Is it possible to just upgrade Tuxedo and not Bouncer? There are no changes to bouncer necessary - I would like to just leave Bouncer alone even if it's not on the latest version.

Thanks!

Comment 1

[Laura Thomson :laura]

It's all in the same repo, so that sounds challenging.

Comment 2

[Chris Turra [:cturra]]

since bouncer is in the tuxedo repo, i don't think there is a clean way for us to update one and not the other.

  https://github.com/mozilla/tuxedo/tree/master/bouncer


tho, your git foo is probably stronger than mine, so i am open to suggestions.

Comment 3

[Laura Thomson :laura]

cturra: can you tell me what hash we're running in prod? If there are no bouncer changes I'm ok.

Buuuut....tomorrow is a Firefox release. Let's not do this now if that's ok.

Comment 4

[Chris Turra [:cturra]]

(In reply to Laura Thomson :laura from comment #3)
> cturra: can you tell me what hash we're running in prod? If there are no
> bouncer changes I'm ok.

production is currently running:

[[e-mail]1 tuxedo]# git log -n 1 --pretty=oneline
897ab227cef9437c0ff6345f472008f838e1dc3f Merge pull request #32 from brandonsavage/fixbouncerform


> 
> Buuuut....tomorrow is a Firefox release. Let's not do this now if that's ok.

i completely agree, it'd seem safest to wait until after the release has made it's way out to the majority of our user base.

Comment 5

[Robert Helmer [:rhelmer]]

Ah I guess I had been assuming bouncer/tuxedo were on totally separate nodes and the code could be update separately - no problem though, I will take a look and see if there have been changes in the bouncer parts of the git repo above the revision mentioned in comment 4 - I would expect not, but good to double-check.

No rush on this from my side, waiting until after release is out of the way WFM

Comment 6

[Robert Helmer [:rhelmer]]

Looks like we don't have any changes to bouncer in between the sha asked for in comment 0 and the one currently in production (comment 4):

$ git diff --stat 897ab227cef9437c0ff6345f472008f838e1dc3f..598b9eeafa1e08b044f60d88ded7aa917e24e38b
 .gitmodules                                  | 2 +-
 apps/api/templates/api/docs/product_add.html | 2 ++
 apps/api/views.py                            | 3 ++-
 vendor                                       | 2 +-
 4 files changed, 6 insertions(+), 3 deletions(-)

Comment 7

[Chris Turra [:cturra]]

i just wanted to check in on this. 27.0{.1} has now been shipped and unthrottled so we're probably in the clear here. any objections?

Comment 8

[Robert Helmer [:rhelmer]]

(In reply to Chris Turra [:cturra] from comment #7)
> i just wanted to check in on this. 27.0{.1} has now been shipped and
> unthrottled so we're probably in the clear here. any objections?

We are fine from my perspective - what does QA say?

Comment 9

[Matt Brandt [:mbrandt]]

I think we're good on stage - automation is purring along with green passes as expected.

Comment 10

[Chris Turra [:cturra]]

push to prod complete. :rhelmer has pinged the fine folks in qa to makes sure all the tests are still green. will mark this bug as r/fixed.

Comment 11

[Matt Brandt [:mbrandt]]

From the QA side of the world; bumping the bug to QA verified. Bouncer.prod tests are still green like Kermit the Frog.