Lumpy logs present here: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/769536/lumpy/

@abodeti, Feel free to move release block label if auto update works.

AU post install is failed:  Execution failed (127): flashrom -p host  -r _current/bios.bin


more log info:
-----------------------------------------------------------------------
[0927/162634:INFO:postinstall_runner_action.cc(166)] Performing postinst (postinst at /tmp/.org.chromium.Chromium.O9lNtq/postinst) installed on device /dev/sda5 and mountable device /dev/sda5
[0927/162634:INFO:postinstall_runner_action.cc(173)] Format file for new postinst is: data
[0927/162652:INFO:subprocess.cc(152)] Subprocess exited with si_status: 1
[0927/162652:INFO:subprocess.cc(156)] Subprocess output:
dm:dm bht[DEBUG] Setting block_count 317440
dm:dm bht[DEBUG] Setting depth to 3.
dm:dm bht[DEBUG] depth: 0 entries: 1
dm:dm bht[DEBUG] depth: 1 entries: 20
dm:dm bht[DEBUG] depth: 2 entries: 2480
PostInstall Configured: (B, /dev/sda5, /dev/sda4, /dev/sda12)

FROM (rootfs):
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_BOARD_APPID={A854E62E-9CB3-4DBE-8BBE-88C48FD65787}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_APPID={A854E62E-9CB3-4DBE-8BBE-88C48FD65787}
CHROMEOS_RELEASE_BOARD=lumpy-signed-mp-v4keys
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_BUILDER_PATH=lumpy-release/R63-9977.0.0
CHROMEOS_RELEASE_BUILD_NUMBER=9977
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_CHROME_MILESTONE=63
CHROMEOS_RELEASE_DESCRIPTION=9977.0.0 (Official Build) dev-channel lumpy 
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=dev-channel
CHROMEOS_RELEASE_VERSION=9977.0.0
DEVICETYPE=CHROMEBOOK
GOOGLE_RELEASE=9977.0.0

FROM (stateful):
CHROMEOS_IS_POWERWASH_ALLOWED=false
CHROMEOS_RELEASE_TRACK=dev-channel

TO:
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_BOARD_APPID={A854E62E-9CB3-4DBE-8BBE-88C48FD65787}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_APPID={A854E62E-9CB3-4DBE-8BBE-88C48FD65787}
CHROMEOS_RELEASE_BOARD=lumpy-signed-mp-v4keys
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_BUILDER_PATH=lumpy-release/R63-9980.0.0
CHROMEOS_RELEASE_BUILD_NUMBER=9980
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_CHROME_MILESTONE=63
CHROMEOS_RELEASE_DESCRIPTION=9980.0.0 (Official Build) dev-channel lumpy 
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=dev-channel
CHROMEOS_RELEASE_VERSION=9980.0.0
DEVICETYPE=CHROMEBOOK
GOOGLE_RELEASE=9980.0.0

ChromeosChrootPostinst(9977.0.0)
Set boot target to /dev/sda5: Partition 5, Slot B
SetImage
KERNEL_CONFIG: console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=91b5896b0c5ce84665780971ac64381ffdd75fab salt=dc43e027d7b84cb9d95a512e1d8d46f448ec2bc42f560bf12c565b6246eab3a2" noinitrd vt.global_cursor_default=0 kern_guid=%U add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3  
Setting up verity.
Finished after 15 seconds.
Clearing network driver boot cache: /var/lib/preload-network-drivers.
Syncing filesystems before changing boot order...
Finished after 2 seconds.
Updating Partition Table Attributes using CgptManager...
Updated kernel 4 with Successful = 0 and NumTriesLeft = 6
Checking /mnt/stateful_partition/unencrypted permission.
Permission is ok.
Unlinked file /var/lib/ureadahead/pack
Starting firmware updater (/tmp/.org.chromium.Chromium.O9lNtq/usr/sbin/chromeos-firmwareupdate --mode=autoupdate)
Command: /tmp/.org.chromium.Chromium.O9lNtq/usr/sbin/chromeos-firmwareupdate --mode=autoupdate
Starting Google_Lumpy firmware updater v3 (autoupdate)...
 - Updater package: [Google_Lumpy.2.111.0 / 02WQA015]
 - Current system:  [RO:Google_Lumpy.2.111.0 [RO_NORMAL], ACT:Google_Lumpy.2.111.0 / 02WQA015]
Warning: wpsw_cur is not availble, using wpsw_boot (1)
 - Write protection: Hardware: ON, Software: Main=ON
 * invoke: flashrom -p host  -r _current/bios.bin
 Execution failed (127): flashrom -p host  -r _current/bios.bin
 Messages:
./updater3.sh: 457: flashrom -p host  -r _current/bios.bin: not found
ERROR: Execution FAILED.
ERROR: Execution failed: ./updater3.sh (error code = 1)
Finished after 1 seconds.
Failed Command: /tmp/.org.chromium.Chromium.O9lNtq/usr/sbin/chromeos-firmwareupdate --mode=autoupdate - Exit Code 1
Firmware update failed (error code: 1).
Rolling back update due to failure installing required firmware.
Successfully updated GPT with all settings to rollback.
PostInstall Failed

Deleted: update_engine.20170927-162322.txt 50.4 KB

update_engine.20170927-162322.txt 50.4 KB View Download

Reproduced only with recovery image but not with test image.

 Issue 769602  has been merged into this issue.

Tom if you have a chance could you please look at this?

"""Execution failed (127): flashrom -p host  -r _current/bios.bin"""

A quick look, the exit code 127, means the command not found, probably missing the flashrom binary?

Able to reproduce this issue on 9984.0.0

Not sure if it is related to the recent change on flashrom from static linkage to dynamic linkage.
https://chromium-review.googlesource.com/668352

+hungte@

That's known to be fixed.