ssh: Could not resolve hostname | provision: FAIL: command execution error, completed successfully |
|||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-paladin/builds/12760 https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-autotest-results/o/66997468-chromeos-test/chromeos4-row8-rack13-host19/status.log /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_EeGxEHssh- master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos4-row8-rack13-host19 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::verify|verify_software|check_diskspace] -> ssh_run(df -PB 1000000 /mnt/stateful_partition | tail -1)\";fi; df -PB 1000000 /mnt/stateful_partition | tail -1" Exit status: 255 Duration: 0.0610630512238 stderr: ssh: Could not resolve hostname chromeos4-row8-rack13-host19: No address associated with hostname Why would the drone suddenly not be able to resolve this hostname. Is something weird going on with our dns?
,
Jun 21 2016
Any idea why we might have had a dns flake at this time?
,
Oct 3 2016
Is this still a problem? or we are OK.
,
Nov 1 2016
Stall, close this ticket |
|||
►
Sign in to add a comment |
|||
Comment 1 by johndhong@chromium.org
, Jun 17 2016