Provision Fail: AC power is not plugged in, completed successfully, servod not running on chromeos4-row9-rack11-host12-servo port 9999 |
|||||||||||||
Issue descriptionARC++ ChromeOS veyron_minnie-paladin test failed on provision error: FAIL: AC power is not plugged in, completed successfully, servod not running on chromeos4-row9-rack11-host12-servo port 9999 Builder page: http://shortn/_UcoxIKVwcY Error log: http://shortn/_nDzQkvQGXA
,
Oct 3 2016
$ dut-status -f chromeos4-row9-rack11-host12
chromeos4-row9-rack11-host12
2016-10-02 22:57:58 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/207030-repair/
2016-10-02 22:39:36 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/206950-provision/
2016-10-02 20:39:16 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78996045-chromeos-test/
2016-10-02 20:38:49 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/206573-reset/
2016-10-02 20:36:50 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78996046-chromeos-test/
2016-10-02 20:20:47 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/206527-provision/
2016-10-02 16:56:57 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78986821-chromeos-test/
2016-10-02 16:56:32 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/206134-reset/
2016-10-02 16:54:36 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78986817-chromeos-test/
2016-10-02 16:38:38 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/206102-provision/
2016-10-02 14:39:44 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78975938-chromeos-test/
2016-10-02 14:39:06 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/205586-reset/
2016-10-02 14:37:01 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78975904-chromeos-test/
2016-10-02 14:16:54 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/205511-provision/
2016-10-02 12:11:52 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78953715-chromeos-test/
2016-10-02 12:11:34 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/205246-reset/
2016-10-02 12:09:43 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78953711-chromeos-test/
2016-10-02 11:55:55 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/205215-provision/
2016-10-02 09:20:41 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78946762-chromeos-test/
2016-10-02 09:20:05 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/204933-reset/
2016-10-02 09:17:27 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78946757-chromeos-test/
2016-10-02 09:03:26 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/204901-provision/
2016-10-02 02:35:41 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78910465-chromeos-test/
2016-10-02 02:35:21 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/203694-reset/
2016-10-02 02:33:18 -- http://cautotest/tko/retrieve_logs.cgi?job=/results/78910444-chromeos-test/
2016-10-02 02:18:29 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row9-rack11-host12/203650-provision/
Next step, examine repair log.
,
Oct 3 2016
START ---- repair timestamp=1475474281 localtime=Oct 02 22:58:01 GOOD ---- verify.ssh timestamp=1475474282 localtime=Oct 02 22:58:02 GOOD ---- verify.brd_config timestamp=1475474282 localtime=Oct 02 22:58:02 GOOD ---- verify.ser_config timestamp=1475474282 localtime=Oct 02 22:58:02 FAIL ---- verify.job timestamp=1475474283 localtime=Oct 02 22:58:03 servod not running on chromeos4-row9-rack11-host12-servo port 9999 START ---- repair.restart timestamp=1475474283 localtime=Oct 02 22:58:03 GOOD ---- verify.ssh timestamp=1475474304 localtime=Oct 02 22:58:24 GOOD ---- verify.brd_config timestamp=1475474304 localtime=Oct 02 22:58:24 GOOD ---- verify.ser_config timestamp=1475474305 localtime=Oct 02 22:58:25 GOOD ---- verify.job timestamp=1475474305 localtime=Oct 02 22:58:25 GOOD ---- verify.servod timestamp=1475474311 localtime=Oct 02 22:58:31 GOOD ---- verify.pwr_button timestamp=1475474311 localtime=Oct 02 22:58:31 GOOD ---- verify.lid_open timestamp=1475474311 localtime=Oct 02 22:58:31 END GOOD ---- repair.restart timestamp=1475474311 localtime=Oct 02 22:58:31 GOOD ---- verify.update timestamp=1475474315 localtime=Oct 02 22:58:35 GOOD ---- verify.PASS timestamp=1475474315 localtime=Oct 02 22:58:35 GOOD ---- verify.ssh timestamp=1475474321 localtime=Oct 02 22:58:41 FAIL ---- verify.power timestamp=1475474321 localtime=Oct 02 22:58:41 AC power is not plugged in START ---- repair.rpm timestamp=1475474321 localtime=Oct 02 22:58:41 FAIL ---- repair.rpm timestamp=1475474321 localtime=Oct 02 22:58:41 Client call exception: <Fault 1: "<class 'autotest_lib.site_utils.rpm_control_system.rpm_infrastructure_exception.RPMInfrastructureException'>:Can not retrieve complete rpm informationfrom AFE for chromeos4-row9-rack11-host12, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."> END FAIL ---- repair.rpm timestamp=1475474321 localtime=Oct 02 22:58:41 GOOD ---- verify.cros timestamp=1475474325 localtime=Oct 02 22:58:45 GOOD ---- verify.good_au timestamp=1475474326 localtime=Oct 02 22:58:46 GOOD ---- verify.writable timestamp=1475474326 localtime=Oct 02 22:58:46 GOOD ---- verify.tpm timestamp=1475474327 localtime=Oct 02 22:58:47 GOOD ---- verify.python timestamp=1475474327 localtime=Oct 02 22:58:47 START ---- repair.au timestamp=1475474327 localtime=Oct 02 22:58:47 GOOD ---- verify.ssh timestamp=1475475798 localtime=Oct 02 23:23:18 GOOD ---- verify.python timestamp=1475475799 localtime=Oct 02 23:23:19 GOOD ---- verify.cros timestamp=1475475803 localtime=Oct 02 23:23:23 GOOD ---- verify.power timestamp=1475475803 localtime=Oct 02 23:23:23 END GOOD ---- repair.au timestamp=1475475803 localtime=Oct 02 23:23:23 GOOD ---- verify.PASS timestamp=1475475803 localtime=Oct 02 23:23:23 INFO ---- repair timestamp=1475475803 localtime=Oct 02 23:23:23 Can't repair label 'pool:cq'. INFO ---- repair timestamp=1475475803 localtime=Oct 02 23:23:23 Can't repair label 'arc'. INFO ---- repair timestamp=1475475803 localtime=Oct 02 23:23:23 Can't repair label 'board:veyron_minnie'. INFO ---- repair timestamp=1475475803 localtime=Oct 02 23:23:23 Can't repair label 'cros-version:veyron_minnie-paladin/R55-8858.0.0-rc2'. END GOOD ---- repair timestamp=1475475803 localtime=Oct 02 23:23:23 chromeos4-row9-rack11-host12 repaired successfully
,
Oct 3 2016
Is there some reason to believe we have no working rpm for this DUT?
,
Oct 3 2016
EC could not reflect the correct status of 'Line Power', .i.e. 'AC power' before rebooting the DUT. That's why it works after reboot, but we have rpm issue.
,
Oct 3 2016
,
Oct 3 2016
RPM issue should be fixed now for that rack
* No RPM entry in database *
johndhong@phobrz:~/chromiumos$ manage_powerunit_info list -m chromeos4-row9-rack11-host12
INFO:root:Connected to cautotest
chromeos4-row9-rack11-host12,,,,
* Adding entry into database *
johndhong@phobrz:~/chromiumos$ manage_powerunit_info -f /tmp/dut_rpm.csv upload
INFO:root:Connected to cautotest
Upload rpm mapping from /tmp/dut_rpm.csv, are you sure? (y/N) y
INFO:root:Adding host attribues to chromeos4-row9-rack11-host1: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A1'}
DEBUG:root:No host named chromeos4-row9-rack11-host2
INFO:root:Adding host attribues to chromeos4-row9-rack11-host3: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A3'}
DEBUG:root:No host named chromeos4-row9-rack11-host4
DEBUG:root:No host named chromeos4-row9-rack11-host5
DEBUG:root:No host named chromeos4-row9-rack11-host6
INFO:root:Adding host attribues to chromeos4-row9-rack11-host7: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A7'}
DEBUG:root:No host named chromeos4-row9-rack11-host8
DEBUG:root:No host named chromeos4-row9-rack11-host9
DEBUG:root:No host named chromeos4-row9-rack11-host10
INFO:root:Adding host attribues to chromeos4-row9-rack11-host11: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A11'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host12: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A12'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host13: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A13'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host14: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A14'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host15: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A15'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host16: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A16'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host17: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A17'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host18: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A18'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host19: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A19'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host20: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A20'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host21: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm2', 'hydra_hostname': None, 'powerunit_outlet': '.A21'}
INFO:root:Adding host attribues to chromeos4-row9-rack11-host22: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A22'}
INFO:root:Adding host attribues to chromeos4-row10-rack11-host1: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A1'}
DEBUG:root:No host named chromeos4-row10-rack11-host2
INFO:root:Adding host attribues to chromeos4-row10-rack11-host3: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A3'}
DEBUG:root:No host named chromeos4-row10-rack11-host4
INFO:root:Adding host attribues to chromeos4-row10-rack11-host5: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A5'}
DEBUG:root:No host named chromeos4-row10-rack11-host6
INFO:root:Adding host attribues to chromeos4-row10-rack11-host7: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A7'}
DEBUG:root:No host named chromeos4-row10-rack11-host8
INFO:root:Adding host attribues to chromeos4-row10-rack11-host9: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A9'}
DEBUG:root:No host named chromeos4-row10-rack11-host10
INFO:root:Adding host attribues to chromeos4-row10-rack11-host11: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A11'}
DEBUG:root:No host named chromeos4-row10-rack11-host12
INFO:root:Adding host attribues to chromeos4-row10-rack11-host13: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A13'}
DEBUG:root:No host named chromeos4-row10-rack11-host14
INFO:root:Adding host attribues to chromeos4-row10-rack11-host15: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A15'}
DEBUG:root:No host named chromeos4-row10-rack11-host16
INFO:root:Adding host attribues to chromeos4-row10-rack11-host17: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A17'}
DEBUG:root:No host named chromeos4-row10-rack11-host18
INFO:root:Adding host attribues to chromeos4-row10-rack11-host19: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A19'}
DEBUG:root:No host named chromeos4-row10-rack11-host20
INFO:root:Adding host attribues to chromeos4-row10-rack11-host21: {'powerunit_hostname': 'chromeos4-row9_10-rack11-rpm1', 'hydra_hostname': None, 'powerunit_outlet': '.A21'}
DEBUG:root:No host named chromeos4-row10-rack11-host22
* Confirmed RPM entry into database *
johndhong@phobrz:~/chromiumos$ manage_powerunit_info list -m chromeos4-row9-rack11-host12
INFO:root:Connected to cautotest
chromeos4-row9-rack11-host12,chromeos4-row9_10-rack11-rpm1,.A12,,
,
Oct 4 2016
,
Oct 4 2016
,
Nov 3 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by cn...@chromium.org
, Oct 3 2016