Is this a build problem ?

If I click on every 53 parrot-ivb build from  https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?boards=parrot-ivb&milestone=53&chromeOsVersion=&chromeVersion=&startTimeFrom=&startTimeTo=#/
I got blank firmware version.

but if i goto 52 https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?boards=parrot-ivb&milestone=52&chromeOsVersion=&chromeVersion=&startTimeFrom=&startTimeTo=#/
all parrot-ivb returns Google_Parrot.2685.54.0

might not be related, but i filed https://b.corp.google.com/u/0/issues/30193565

Yeah, seems like a build issue. Another clue from the update_engine log:
No firmware updates available.
Rolling back update due to failure installing required firmware.

As you point out in #4, it appears that the firmware image isn't being bundled with the AU image.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

AU failed on M53 builds. 

Failed Recovery install too. attached recovery log. 

Deleted: recovery.log 110 KB

recovery.log 110 KB View Download

From recovery log:
==================================
KERNEL_CONFIG: console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-1 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="2 vboot none ro 1,0 2545920 bootcache PARTUUID=%U/PARTNROFF=1 2545920 6b003ee529f9588ebade5da7a50cb3bc679b13f5 512 20000 100000, vroot none ro 1,0 2506752 verity payload=254:0 hashtree=254:0 hashstart=2506752 alg=sha1 root_hexdigest=6868068ec832359d1a3f4dcca5a243ea5800ce60 salt=4b602562f36d0aa9d19da95d3440caa4788b0c433a8bd777f023b16ef9da4514" 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 12 seconds.
Clearing network driver boot cache: /var/lib/preload-network-drivers.
Syncing filesystems before changing boot order...
Finished after 0 seconds.
Updating Partition Table Attributes using CgptManager...
Updated kernel 2 with Successful = 1 and NumTriesLeft = 6
Checking /mnt/stateful_partition/unencrypted permission.
RemovePackFiles Failed
Touch(/mnt/stateful_partition/.install_completed) FAILED
No firmware updates available.
Rolling back update due to failure installing required firmware.
Successfully updated GPT with all settings to rollback.
PostInstall Failed
======================================================

removing M53 since this has been moved to M54.

ketakid@, I don't follow #10. Could you please elaborate? What has been moved to M54? 

This is a M53 problem and apply only to 53, not 54.

the automated sheriffbot had moved this bug to M54 per comment#6. That's what i was referring to. This is a recovery scenario which mostly applies to Stable builds. Is there a reason we are blocking dev for that?

Facing this issue with both Auto-Update and Recovery. So this issue should be a dev blocker.

Note: Recovery issues blocks only stable if Auto-Update works fine.

dshi@/kevcheng@ - can you please confirm that there have been no builder config changes to these builders for parrot/ivb/mario?

reinauer@ _ can you please confirm there haven't been any fw changes for these boards?

There doesn't seem to be any recent changes with regards to parrot/ivb/mario.

sontis@ We didn't see this issue on the last dev we did. so something has definitely changed between that build and this one. 

Firmware version is not displaying for parrot and parrot-ivb in M53 build.
Please find the attachments.

Deleted: parrot.png 28.4 KB

	parrot.png 28.4 KB View Download

Deleted: parrot_ivb.png 27.8 KB

	parrot_ivb.png 27.8 KB View Download

There are no pending firmware updates for parrot (that I know of).

30193565 definitely looks like the same issue, not sure why it was closed as works as intended.

I noticed this:
Checking /mnt/stateful_partition/unencrypted permission.
RemovePackFiles Failed
Touch(/mnt/stateful_partition/.install_completed) FAILED


Is there an issue with stateful? 

Hung-Te, can you please have a look what might be going wrong here?

The firmware updater is running successfully:

[0715/173107:INFO:subprocess.cc(156)] Subprocess output:
Starting Google_Parrot firmware updater v3 (bootok)...
 - Updater package: [Google_Parrot.2685.54.0 / 00BE107A00]
 - Current system:  [RO:Google_Parrot.2685.54.0 [RO_NORMAL], ACT:Google_Parrot.2685.54.0 / 00BE107A00]
Warning: wpsw_cur is not availble, using wpsw_boot (1)
 - Write protection: Hardware: ON, Software: Main=off
Warning: EC FMAP layout file is overridden by ec.layout.
 * invoke: flashrom -p host -i RW_SECTION_A:_dup2_temp_from -i RW_SECTION_B:_dup2_temp_to -r _dup2_temp_image
Firmware update (bootok) completed.

Re#22

 The 'bootok' is executed by the 'current image', not the 'imaged downloaded for AU'.
 It's true the images do not have firmware updater, and it's caused by
   https://chrome-internal-review.googlesource.com/#/c/267686/
 Same as my comment - it may break AU.

 The CL was later fixed by 
   https://chrome-internal-review.googlesource.com/#/c/268306/

 So 8529~8537 are all broken.
 
M53 unfortunately cuts the branch at 8530, which falls into the broken period.

Daisuke, please cherry-pick change 268306 into M53, thanks!

Daisuke, can we get this change cherry picked into M53 asap? I can approve merge right away.

https://chrome-internal-review.googlesource.com/#/c/270113/

AU is fine on parrot-M53(8530.35.0) but not tested on mario because of build is missing. 

Recovery is working fine.