1282804 - Please deploy loop standalone 1.4.2 to STAGE

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect)

Description

[Mark Banner (:standard8)]

------------------
RELEASE NOTES
------------------
https://github.com/mozilla/loop/blob/v1.4.2/CHANGELOG.md

COMPARISONS
https://github.com/mozilla/loop/compare/v1.3.0...v1.4.2

TAGS
https://github.com/mozilla/loop/releases/tag/v1.4.2
https://github.com/mozilla/loop/commit/1e5b749705a0cf43ff97fea73d8311a33441c8a9

Notes: We're looking to get this to production this week please, in prepartion for add-on releases next week.

Comment 1

[Mark Banner (:standard8)]

UI visible changes:

- There's now a notification in the text chat when a peer joins the room.

Metrics:

- We now log an additional event that will tell us if the connection has succeeded or not.

Potential stability fixes:

- iceRestart is no longer set to true on the first connection.

Comment 2

[Chris Hartjes [:grumpy][:chartjes]]

==========
PRE-DEPLOYMENT TEST
==========

Ran my hybrid Marionette tests on Firefox Beta (48.0b4 and Firefox Nightly (49.0a1) that do the following:

end-2-end test calls (shared URL) - OK
Video/audio mute/unmute - OK
messaging - OK 
Tab & window-sharing - OK
privacy & ToS links - OK
Feedback screens - OK
push notifications - OK

Configuration check tests ran successfully using the following values:

location =  https://www.mozilla.org/firefox/hello/
root = https://call.stage.mozaws.net
loop_server = https://loop.stage.mozaws.net
loop_server_version = 0.21.3
loop_server_push_server_config = https://loop.stage.mozaws.net/push-server-config
loop_server_push_server_uri = wss://autopush.stage.mozaws.net
loop_fxos_app_name = Hello Stage
feedbackProductName = Loop
privacyWebsiteUrl = https://www.mozilla.org/privacy/firefox-hello/
legalWebsiteUrl = https://www.mozilla.org/about/legal/terms/firefox-hello/
roomsSupportUrl = https://support.mozilla.org/kb/group-conversations-firefox-hello-webrtc
guestSupportUrl = https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode
unsupportedPlatformUrl = https://support.mozilla.org/kb/which-browsers-will-work-firefox-hello-video-chat
learnMoreUrl = https://www.mozilla.org/hello/
homePage = https://github.com/mozilla-services/loop-server/
fakeTokBox = False
fxaOAuth = True
name = mozilla-loop-server
version = 0.21.3


platform darwin -- Python 2.7.11, pytest-2.9.1, py-1.4.31, pluggy-0.3.1 -- /Users/chartjes/mozilla-services/services-test/loop/venv/bin/python2.7
cachedir: config-check/.cache
rootdir: /Users/chartjes/mozilla-services/services-test/loop/config-check, inifile:
collected 4 items

config-check/test_config_check.py::test_header PASSED
config-check/test_config_check.py::test_server_config PASSED
config-check/test_config_check.py::test_server_response PASSED
config-check/test_config_check.py::test_push_server_config PASSED

QA approved for deployment to staging.

Comment 3

[Daniel Maher [:phrawzty]]

We having problems getting this deployment to function. We don't think it's an application issue.  There's something going on with our stack health monitoring mechanism.  Until we can get this issue resolved, we won't be able to deploy a new Stage Loop Standalone stack.  Unfortunately, this also means we'll have to put any Prod deployments of same on hold.

Comment 4

[Daniel Maher [:phrawzty]]

The AMI was sufficiently stale that the AWS lib was failing in obscure ways (cloud-init was *silently* failing, for example). This meant that everything looked fine except for, like, one api call - and that one api call was causing the stack to never return 0.

Anyway, I updated the AMI and performed a handful of deployments - each one went green, so that's good. I left the last one in place, along with the promoted DNS, so it should be ready to test at QA's convenience. :)

Comment 5

[Chris Hartjes [:grumpy][:chartjes]]

I have retested staging as per https://bugzilla.mozilla.org/show_bug.cgi?id=1282804#c2 and everything passed.

Comment 6

[Daniel Maher [:phrawzty]]

From my perspective this bug can be closed out. Yes/no?

Comment 7

[Mark Banner (:standard8)]

(In reply to Daniel Maher [:phrawzty] from comment #6)
> From my perspective this bug can be closed out. Yes/no?

Chris, what do you think?

Comment 8

[Chris Hartjes [:grumpy][:chartjes]]

QA approved.