If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Deploy the latest Loop-Client code to Stage

VERIFIED FIXED

Status

Cloud Services
Operations: Deployment Requests
VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: jbonacci, Assigned: mostlygeek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

Comment hidden (empty)
(Reporter)

Updated

3 years ago
Whiteboard: [qa+]
(Assignee)

Updated

3 years ago
Assignee: nobody → bwong
(Assignee)

Updated

3 years ago
Blocks: 1022886
(Assignee)

Comment 1

3 years ago
Deployed the newest loop-client code/stack. 
The endpoint, https://call.stage.mozaws.net is pointed to it now.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

3 years ago
Will look into Verifying this one tomorrow...
I doesn't seams to work from here.
(Assignee)

Updated

3 years ago
Blocks: 1021891
(Assignee)

Comment 4

3 years ago
Reopening this bug as we had to update the puppet-code a bit. We had a weird AWS issue yesterday and couldn't deploy to stage/dev. That looks to be resolved now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 5

3 years ago
New stack deploy and is now working. https://call.stage.mozaws.net is pointed to it.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

3 years ago
Not much to verify here since it is just static files.

Verified the AWS info for the stack, ELB, and instance.
Verified the instance OS, processes, files, and logs.

https://call.stage.mozaws.net/config.js
returns the following:
var loop = loop || {};
loop.config = {serverUrl: 'https://https://loop.stage.mozaws.net'};


So, I think we are good with the client side of Stage and can focus on the verification of the server side of Stage...
Status: RESOLVED → VERIFIED

Comment 7

3 years ago
loop.config = {serverUrl: 'https://https://loop.stage.mozaws.net'}; looks buggy to me. I think this is because of a hack I added on Friday that we should fix at https://github.com/mozilla-services/puppet-config/blob/master/loop/modules/loop_client/templates/client_config.js#L2.
(Reporter)

Comment 8

3 years ago
Bad enough I posted that and Verified w/o careful inspection.
Please fix and we can redeploy.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 9

3 years ago
:mostlygeek updated this a short time ago...
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 10

3 years ago
OK. I am calling this one good.
Once I Verify the loop-server Stage, I will open the appropriate Prod tickets...
Status: RESOLVED → VERIFIED
(Reporter)

Updated

3 years ago
Blocks: 1024180
You need to log in before you can comment on or make changes to this bug.