ELB treats a mozilla-releases or mozilla-archived web-server as "unhealthy"
Categories
(Webtools :: Searchfox, defect)
Tracking
(Not tracked)
People
(Reporter: kats, Assigned: kats)
References
(Regression)
Details
When replacing read_json.py with jq I apparently broke this line because now DEFAULT_TREE_NAME is coming out as the string null (for the mozilla-releases and mozilla-archived channels). Which means that the help.html file doesn't get linked into the docroot, and a GET / request on the webserver returns a 404. This doesn't have any user-visible impact (because ELB routes the top-level / request to the release web-server, which doesn't suffer from this problem) but it causes ELB to report the server as unhealthy.
|
Assignee | |
Comment 1•5 years ago
|
||
https://github.com/stedolan/jq/issues/1583 and some experimentation shows there doesn't seem to be a good way to get jq to not emit null in this case. We can either populate the default_tree field on the configs, or explicitly check for null in web-server-setup.sh, or both.
|
|
Assignee | |
Comment 2•5 years ago
|
||
I was wrong, there is a way!
|
|
Assignee | |
Updated•5 years ago
|
Description
•