faft test failed: No answer to ssh from 192.168.231.1 |
||||
Issue descriptionDUT and servod are up and running, firmware_FAFTSetup completed without issues. However, when trying to run test_suites:faft_setup, test was failed due to "No answer to ssh from 192.168.231.1" autoserv had ERROR: repair:0332] Failed: host is available via ssh I've tried ssh from moblab to DUT and it was ok, DUT ssh to Moblab showed password prompt. root@DUT had authorized_keys -> /usr/share/chromeos-ssh-config/keys/authorized_keys and id_rsa.pub -> /usr/share/chromeos-ssh-config/keys/id_rsa.pub The DUT is veyron_minnie with R59-9460.73.1, FW:R41-6588.237 (also tried 6588.197)
,
Aug 2 2017
dchan: FYI, the new moblab doc link is https://sites.google.com/a/chromium.org/dev/chromium-os/testing/moblab The ssh setup section is https://docs.google.com/document/d/10CAXkrL1_THm2G9Y-Az1W2Su9SnEE9HJJY0RvTVpBkM/edit#heading=h.ddbz5yr0t463 ===== dshi: What's the moblab's IP? I guess 192.168.231.1 is the local IP in the moblab setup. What account did you use to log in moblab? user moblab should be used. Please double check the ssh config
,
Aug 3 2017
@dshi the moblab IP was 172.30.251.172 (Google internal) but it doesn't matter here since we are not testing remote access. 192.168.231.1 is moblab itself, DUT (192.168.231.100) was trying to ssh back but failed.
,
Nov 10 2017
,
Jan 12 2018
FAFT on moblab is being de-prioritized archiving this bug |
||||
►
Sign in to add a comment |
||||
Comment 1 by chlin@google.com
, Aug 2 2017