chaos-lab server is not reachable |
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. ping the system - 172.22.39.251 fails 2. create an ssh tunnel - fails ssh -L 5905:localhost:5900 root@172.22.39.251 -nNT 3. both the above failures are sporadic, sometimes the server network is up, sometimes it's down resulting in interference with test execution What is the expected behavior? The network should always be up allowing for remote management using vnc viewer. What went wrong? network failure Did this work before? N/A Chrome version: 60.0.3112.90 Channel: stable OS Version: Flash Version:
,
Aug 14 2017
,
Aug 14 2017
Unable to triage from Chrome-TE end so adding TE-NeedsTriageHelp label for further investigation
,
Aug 16 2017
,
Aug 16 2017
This is nothing that infra labs supports, I assume probably the chromeos lab?
,
Aug 16 2017
,
Aug 16 2017
,
Aug 17 2017
Seems like this is fixed now. The problem was that: $ nslookup chromeos3-chaosvmmaster.cros.corp.google.com Was returning address: 172.22.39.250 for some machines and 172.22.39.251 for others. It might be caused by a dns cache problem. Yash, Please take a look and see if this is fixed now for you too.
,
Aug 17 2017
172.22.39.251 is still not reachable for me. nslookup gives me the following: $ nslookup chromeos3-chaosvmmaster.cros.corp.google.com Server: 127.0.1.1 Address: 127.0.1.1#53 Non-authoritative answer: Name: chromeos3-chaosvmmaster.cros.corp.google.com Address: 172.22.39.250
,
Aug 17 2017
The hostname is resolving to the correct ip now: 172.22.39.250 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by shahy@google.com
, Aug 11 2017