Chrome side changes: https://chromium.googlesource.com/chromium/src/+log/61.0.3152.0..61.0.3153.0?pretty=fuller&n=10000

chromeos4-row5-rack13-host5 is bad?

host: chromeos4-row5-rack13-host5, status: Repairing, locked: False diagnosis: Working
labels: ['board:link', 'bluetooth', 'video_glitch_detection', 'lightsensor', 'hw_video_acc_enc_h264', 'storage:ssd', 'audio_loopback_dongle', 'os:cros', 'hw_jpeg_acc_dec', 'power:battery', 'ec:cros', 'cts_abi_arm', 'servo', 'cts_abi_x86', 'hw_video_acc_h264', 'webcam', 'link', 'pool:cq', 'internal_display', 'touchpad', 'sku:link_intel_i5_3427u_1800_4_core_2Gb', 'variant:link', 'cros-version:link-release/R60-9592.37.0']
Last 10 jobs within 1:48:00:
3912016 Provision started on: 2017-07-10 21:53:34 status FAIL
3911916 Repair started on: 2017-07-10 20:58:34 status PASS
3911913 Verify started on: 2017-07-10 20:57:32 status FAIL

The error log for the failed login_MultipleSessions:
https://00e9e64bac3c0d9838f4c7122314f372853a941a8168c13ae5-apidata.googleusercontent.com/download/storage/v1/b/chromeos-autotest-results/o/127911948-chromeos-test%2Fchromeos4-row5-rack13-host1%2Fjob_report.html?qk=AD5uMEvvPDmuIKfqZMnhPIKzVuj94KuHlEuceo65Zi4omxqUSjm4xVyvlu4daUueSvuai8LiJKCcdxE9MWVSPpCH1v6E3NGbFuYXGtuWe53WoymydKwlZsNxEHPFVTSoTG9iDv5hyyhPyw769zOvUZzNdwB-GjXAIkM2sT2uBkKr1rebfmDyrmKdbqKYYlSF3qeCYs7WwQ3Mi3PMyeIbWzNaUnhvXGx0dV0avqt_mXvkbdsr_bSHNLAQJEcmVNx--qgMH0KTovw_4Tj0Yc8IlCjIrcPWTwEw0FQifMXFxF6pKggdSmQec5uxeSs2_AVGMM4Z4-9aQhYbsgmUDN-eQrHcgbbQxUSg082tbLokF44nsiQqn-hA4JHlnKIAyNByB6KFnDvsj5DsBwDo5zlg1BjPEy4kXG3kcAe4Ae8kVte0EkbBJ7gLUFObQG0Q1EqM5xV9NWEMLmB3RfG_nO58Bf-fXO104dfxqiRkV7ND0V-qmW1PgKkK19xA5NTx6-IXFah3-XbaJuPRX2l6J_UxnAmdvMgNG7eUtk9DYxyXdfLLfE0-E7SL9E_r-juLyIgE1Wf8xEOTjlhSSO9vInWTZMPORGnAVaX6OkB0ofdtMwU41PqTL2ET4II64udAJH74erKh_UryjVsBAN0ArMVEgwQzFWqszEaZaAMYHGrvlNjtIcjPpLT_id7DVusDFdRht-ugxM5IIQPuYpD9XMpJk1iQKPfIkMAoDtqZw7-DewrEwIfrKctIETU4n3AMZhD1FHB4iiQmDImcFugofNc42P9K66NMw8mg41Zvac3XTZFzdGvEkUnkBFbtG6kBzLNxiQWTGrPxPb4-g6aMuUchYzyIdT1K1m3HvkA3WB_LBcSC8M52Kwt_R6I#

=== Info log ===

STDERR:
File not found.

STDOUT:
File not found.

STATUS:
START login_MultipleSessions login_MultipleSessions timestamp=1499750660 localtime=Jul 10 22:24:20 
FAIL login_MultipleSessions login_MultipleSessions timestamp=1499750667 localtime=Jul 10 22:24:27 Unhandled DBusException: org.chromium.SessionManagerInterface.NoUserNssDb: Cant create session. 
Traceback (most recent call last): 
File /usr/local/autotest/common_lib/test.py, line 818, in _call_test_function 
return func(*args, **dargs) 
File /usr/local/autotest/common_lib/test.py, line 471, in execute 
dargs) 
File /usr/local/autotest/common_lib/test.py, line 348, in _call_run_once_with_retry 
postprocess_profiled_run, args, dargs) 
File /usr/local/autotest/common_lib/test.py, line 381, in _call_run_once 
self.run_once(*args, **dargs) 
File /usr/local/autotest/tests/login_MultipleSessions/login_MultipleSessions.py, line 42, in run_once 
self.__start_session_for(expected_owner) 
File /usr/local/autotest/tests/login_MultipleSessions/login_MultipleSessions.py, line 81, in __start_session_for 
self._session_manager.StartSession(user, ) 
File /usr/local/lib64/python2.7/site-packages/dbus/proxies.py, line 145, in __call__ 
**keywords) 
File /usr/local/lib64/python2.7/site-packages/dbus/connection.py, line 651, in call_blocking 
message, timeout) 
DBusException: org.chromium.SessionManagerInterface.NoUserNssDb: Cant create session. 
END FAIL login_MultipleSessions login_MultipleSessions timestamp=1499750667 localtime=Jul 10 22:24:27 

DMESG:
File not found.

+hidehiko@, who last touched login_MultipleSessions.py
Do you have any idea why this fails?

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/127911948-chromeos-test/chromeos4-row5-rack13-host1/login_MultipleSessions/sysinfo/

2017-07-11T05:24:25.779539+00:00 INFO session_manager[22292]: [INFO:policy_key.cc(53)] No policy key on disk at /home/root/b02d33503f941632bdb4e3c9d220f6cf9e71eadb/session_manager/policy/key

No policy key is available?

Hmm, though I cannot find a culprit CL in the list...?

Oh, the last build was successful. Maybe the test is just flaky?

Yes. In the last build, login_MultipleSessions retried once. So it's flaky.

master-paladin succeeded. I'd keep this bug open to resolve flakienss of login_MutipleSessions.

Filed  crbug.com/740839  for flakiness, and marked this bug as fixed.