New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 720185 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Some stray servers (including non-prod) are reporting weird git repos

Project Member Reported by pho...@chromium.org, May 10 2017

Issue description

See

http://shortn/_HX4vxTOQiH
http://shortn/_IpFWTSoJ22

shuqian-test1 and cros-drone-bak-test1, and  chromeos4-devserver11 have wrong repo addresses in the /chrome/infra/chromeos/sysmon/git/hash metric.

Furthermore, "shuqian-test1" and "cros-drone-bak-test1" shouldn't even be reporting metrics in the first place, right?

Even better would be to join the query in deputy view (https://viceroy.corp.google.com/chromeos/deputy-view?duration=8d) with the prod_hosts/role metric to avoid this problem from affecting the dashboard in the future.
 
If we do that, I think we should do a precomputation like the chrome-infra botmap precomputations.

Comment 2 by pho...@chromium.org, May 10 2017

This query joins the prod_hosts/role metric with the git repo metric: http://shortn/_E4Dfklq7Sv

I'll make a CL to improve the viceroy deputy-view dashboard.

Comment 3 by pho...@chromium.org, May 10 2017

Oh, good idea with the precomputation; the improved performance should be worth it.
Also, try going into those 2 servers and deleting their ts_mon creds. They might not reappear, since I think our puppet rules might only deploy them to prod-like servers.
#4, we aren't restricting ts_mon creds to prod yet because we don't have a reliable way of determining prod from Puppet.
Labels: -Pri-2 Hotlist-Fixit Pri-3
Labels: -Hotlist-Fixit
Can we explicitly state what the goals/actions for this is?  Otherwise not fixit-able
--> ayatane to first deal with the currently unhappy servers (a puppet source update will fix the current problem. Already fix in ToT)
Status: Archived (was: Untriaged)
This bug is very old, is Untriaged, and has no owner.  If it is still relevant, reopen as Untriaged or open a new bug

Sign in to add a comment