it is chromeos6-devserver1. It is down. I think we need to file a bug to the lab team to manually fix this devserver.

Hmmm...  The host still appears in our config files:
    $ grep -l 100.115.174.192 $(findfiles * | grep shadow_con)
    puppet/modules/lab/templates/cautotest_shadow_config.ini.erb
    puppet/modules/lab/templates/afe_shadow_config.ini.erb
    puppet/modules/lab/templates/shard_shadow_config.ini.erb
    puppet/modules/lab/templates/drone_shadow_config.ini.erb
    server_management_lib/tasks/templates/shadow_config_test_push_shard.ini
    server_management_lib/tasks/templates/shadow_config_test_push_master.ini
    server_management_lib/tasks/templates/shadow_config_test_push_drone.ini

... and the host is still down:
    $ ping -c 5 100.115.174.192
    PING 100.115.174.192 (100.115.174.192) 56(84) bytes of data.

    --- 100.115.174.192 ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 4031ms


However, that IP address isn't chromeos6-devserver1:
    $ host chromeos6-devserver1
    chromeos6-devserver1.cros.corp.google.com has address 100.115.185.225

Anyway, not my problem _this week_.

Can we confirm that it's SUPPOSED to not exist before removing it?

chromeos6-devserver1 no longer uses that IP
https://b.corp.google.com/issues/28734200

chromeos6-devserver1 / 100.115.185.225

I can write the CL but I need confirmation that the server is setup to be a fully proper devserver

https://chrome-internal-review.googlesource.com/#/c/272330

Kicking to deputy to confirm devserver is setup properly

CL has been submitted.