+dschimmels, krisr

The hostnames are 

chromeos9-infra-devserver
chromeos9-infra-devserver1
chromeos9-infra-devserver2

Which makes them android lab devservers.

+ richard - if this isn't happening anymore, pls close

(Also, feel free to make this into a fix it / feature request if needed for IP address to hostname)

Still happening (see below).

N.B. CrOS Infra doesn't maintain these servers, so I'm passing the
buck.

$ for h in ${HOSTS[@]}
> do
> ping -c 2 $h
> done
PING chromeos9-infra-devserver.cros.corp.google.com (100.115.99.252) 56(84) bytes of data.

--- chromeos9-infra-devserver.cros.corp.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

PING chromeos9-infra-devserver1.cros.corp.google.com (100.115.99.251) 56(84) bytes of data.

--- chromeos9-infra-devserver1.cros.corp.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

PING chromeos9-infra-devserver2.cros.corp.google.com (100.115.99.250) 56(84) bytes of data.

--- chromeos9-infra-devserver2.cros.corp.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1006ms

ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be closed. Thank you.