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

Issue 813182 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Revive NoDevserverInSubnet alert filtered to relevant subnets

Project Member Reported by pho...@chromium.org, Feb 16 2018

Issue description

Like the subject says
 

Comment 1 by nxia@chromium.org, Feb 16 2018

what's the context here? what subnets are relevant here? 

Comment 2 by pho...@chromium.org, Feb 16 2018

I'm not sure how to determine which subnets are relevant. But we do know that the alert has been firing nonstop for a couple weeks on a particular subnet which we apparently don't care about.

For future reference/rollback, the alert was deleted in https://critique.corp.google.com/#review/186042455

Comment 4 by nxia@chromium.org, Feb 16 2018

If we don't know the relevant subnets, we just keep adding irrelevant subnets to blacklisted_subnet ?

Comment 5 by pho...@chromium.org, Feb 17 2018

ok. Is there a nice way to automatically tell which subnets affect which DUTs, or is it documented somewhere?
I forgot that we have a blacklist. In that case, please add the recent offending subnet to the blacklist and rollback my cl

Comment 7 by pho...@chromium.org, Feb 17 2018

Owner: pho...@chromium.org

Comment 8 by pho...@chromium.org, Mar 29 2018

Status: Archived (was: Assigned)

Sign in to add a comment