shard provision failure |
||
Issue descriptionSeparated from issue 754337 Comment 4 by nxia@chromium.org, Today (14 minutes ago) Delete comment ⚐ I login each machine and delete the lock manually. provision skunk-2 gave an error, should I just re-run the provision command ? [chromeos-skunk-2.mtv.corp.google.com] out: HEAD is now at 11f11de... Add backports.shutil_which [chromeos-skunk-2.mtv.corp.google.com] out: Error: Syntax error at 'user' at /root/chromeos-admin/puppet/modules/lab/manifests/core_cluster.pp:24:5 on node chromeos-skunk-2.mtv.corp.google.com [chromeos-skunk-2.mtv.corp.google.com] out: Error: Syntax error at 'user' at /root/chromeos-admin/puppet/modules/lab/manifests/core_cluster.pp:24:5 on node chromeos-skunk-2.mtv.corp.google.com [chromeos-skunk-2.mtv.corp.google.com] out: Fatal error: sudo() received nonzero return code 1 while executing! Requested: HOME=/root/ FACTER_server_type="autotest-shard" /root/chromeos-admin/puppet/sync_and_run_puppet -f Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "HOME=/root/ FACTER_server_type=\"autotest-shard\" /root/chromeos-admin/puppet/sync_and_run_puppet -f" Comment 5 by shuqianz@chromium.org, Today (7 minutes ago) Delete comment ⚐ bad change https://chrome-internal-review.googlesource.com/c/424469
,
Aug 10 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/64472f1c102276276fa5b1cdd36eeec51b3b57bd commit 64472f1c102276276fa5b1cdd36eeec51b3b57bd Author: xixuan <xixuan@chromium.org> Date: Thu Aug 10 23:43:56 2017
,
Aug 15 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by nxia@chromium.org
, Aug 10 2017