New issue
Advanced search Search tips

Issue 741779 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

paygen_au_canary failures: stateful.tgz does not exist!

Project Member Reported by dhadd...@chromium.org, Jul 12 2017

Issue description

Paygen_au_canary has started failing a lot with this error

Unhandled DevServerException: CrOS auto-update failed for host <HOST>: ChromiumOSUpdateError: Payload /home/chromeos-test/images/canary-channel/<BOARD>/9737.0.0/stateful.tgz does not exist!

This was caused by a recent change to the test:
https://chromium-review.googlesource.com/#/c/544536/

Investigating... 
 
The problem is the stateful payloads are not getting staged in the same directory as the rootfs payloads. 


full test payload from gs://chromeos-releases/... staged at http://100.115.219.133:8082/static/canary-channel/samus/9736.0.0/payloads/payload.bin

Target stateful update from standard location staged at http://100.115.219.133:8082/static/samus-release/R61-9736.0.0/stateful.tgz

So the stateful is getting staged from "standard location" and being put in a different folder within static 
Cc: abod...@chromium.org ka...@chromium.org sdantul...@chromium.org sontis@chromium.org
OK I got it.

The lab does not supply test_archive_uri to the test so when it comes time to stage stateful.tgz for the target update it uses the job_repo_url to figure out the location for the current build instead of figuring out the location based on the target_payload_uri 

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/site_tests/autoupdate_EndToEndTest/autoupdate_EndToEndTest.py?l=679

I'll make a CL now 
Cc: xixuan@chromium.org
CL up at https://chromium-review.googlesource.com/#/c/568390/

Project Member

Comment 5 by bugdroid1@chromium.org, Jul 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/7b8e9b580b9883fc60bee7d26973c6d8d14cb5c8

commit 7b8e9b580b9883fc60bee7d26973c6d8d14cb5c8
Author: David Haddock <dhaddock@chromium.org>
Date: Thu Jul 13 18:44:40 2017

[autotest] Stage stateful to the same location as rootfs payloads.

The autoupdate_EndToEndTest makes use of the devserver cros_au RPC that
expects the rootfs and stateful payloads to be staged within the same
static folder on the devserver.

When run in the lab the test was staging the stateful payload for the
target update in a different location because it was using the job_repo_url
to figure out where stateful is.

This CL makes it look in the same folder for the stateful.

BUG= chromium:741779 
TEST=autoupdate_EndToEndTest passes

Change-Id: I2c8a98d9c532eaef0d4fd5566f22c199fe842c0b
Reviewed-on: https://chromium-review.googlesource.com/568390
Commit-Ready: David Haddock <dhaddock@chromium.org>
Tested-by: David Haddock <dhaddock@chromium.org>
Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org>

[modify] https://crrev.com/7b8e9b580b9883fc60bee7d26973c6d8d14cb5c8/server/site_tests/autoupdate_EndToEndTest/autoupdate_EndToEndTest.py

Status: Fixed (was: Untriaged)
Issue 742919 has been merged into this issue.
Status: Verified (was: Fixed)
Labels: FixedByAURewrite

Sign in to add a comment