While investigating a provision failure (in cq https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16857) , I went to look at the repair job logs.

$ dut-status -f chromeos4-row3-rack2-host12
chromeos4-row3-rack2-host12
    2017-11-08 11:09:19  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack2-host12/227458-repair/
    2017-11-08 10:29:54  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack2-host12/227352-provision/
    2017-11-08 07:32:12  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/154865964-chromeos-test/
    2017-11-08 07:31:57  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack2-host12/227235-reset/
    2017-11-08 07:31:27  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/154865968-chromeos-test/
    2017-11-08 07:31:12  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack2-host12/227223-reset/
    2017-11-08 07:30:41  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/154865957-chromeos-test/


The repair appears to have succeeded via rpm power cycle, but no logs were collected from the DUT.

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos4-row3-rack2-host12/227458-repair/20170811110918/

That makes it nearly impossible to diagnose the previous provision or boot issue (unless the DUT is still unused/idle from it's last run).