Loop server Stage — Configuration is broken ?

RESOLVED WONTFIX

Status

Cloud Services
Operations
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: alexis, Assigned: mostlygeek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8445851 [details]
loop-server stage configuration file

The deployment for the Loop Stage server is wrong.

 - The Instance was not linked to the right ELB
 - The configuration file is wrong, a number of fields are mis-configured:
    - "protocol" should be set to "https";
    - "sessionSecret" contains the default value;
    - tokbox API keys aren't set (you can see the SET_ME);
    - webAppURL points to dev (it should be stage);
    - statsd configuration doesn't look correct (there is a double dot)

Also, we're not getting errors when the ELB is 503ing, that really should be the case (or maybe someone got alterted already?)

It's possible we hooked to an old machine, that was the only one listed in the AWS console. If so, I don't know what's hapenning: maybe healthcheck failed and no new machine was spawned?

Benson, can you have a look?
(Assignee)

Comment 1

4 years ago
Which machine are you looking at? 

The loop-server cloudformation (us-east-1, loop-server-stage) has 0 running servers.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
(Assignee)

Comment 2

4 years ago
Oops. 

It has 0 running servers because I scaled it down since I am waiting on the next release candidate before deploying another stage.
(Reporter)

Comment 3

4 years ago
okay, then it had one still running that needs to be turned off: ec2-54-87-84-158.compute-1.amazonaws.com
Interesting. That one is not on my list of (former) loop-server stage hosts...
Looks like a one-off special:
i-23cd6173 (loop app server (ulfr-devstack-loop))Public DNS: ec2-54-87-84-158.compute-1.amazonaws.com
You need to log in before you can comment on or make changes to this bug.