chromeos-server158.cbf is using the wrong DB. |
||||
Issue descriptionBefore CL:*575505 every lab server used a hardcoded reference to the master be in global_config.ini. Now, puppet should be overriding that value with the current primary database, but chromeos-server158.cbf doesn't seem to get the message, even after I forced a puppet run. It's shadow_config.ini hasn't been updated since Dec, and is missing the new entry. atest server list shows: Hostname : chromeos-server158.cbf.corp.google.com Status : primary Roles : afe Attributes : {} Date Created : 2017-09-14 19:04:51 Date Modified: 2017-09-14 19:04:51 Note : None
,
Feb 22 2018
,
Feb 23 2018
,
Feb 23 2018
The issue is that puppet doesn't have a role assigned to the server, so.... doesn't do nuthin much.
,
Feb 23 2018
> It's only mentioned in puppet via: > lab/manifests/autotest_proxy.pp: $swarming_afe = 'http://chromeos-server158.cbf.corp.google.com' ... meaning it has no role assigned. Meaning it doesn't know how to calculate a proper shadow_config.ini. Meaning it's continuing to use the database server as it was configured on 12/6/2017. Which, of course, causes this bug.
,
Feb 23 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/2ab17374e05ff3ac8dfd83534e8fd15ff5779678 commit 2ab17374e05ff3ac8dfd83534e8fd15ff5779678 Author: Richard Barnette <jrbarnette@google.com> Date: Fri Feb 23 00:12:43 2018
,
Feb 23 2018
Richard forced a puppet run, and the server is now able to load web pages.
,
Feb 23 2018
This seems fixed. It can certainly load web pages with value values now. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, Feb 22 2018