[Canary] Failed at autoupdate_EndToEndTest.paygen_au_canary_full on v3.14 kernel (encryption changes landed in M54) |
|||||||||||||
Issue descriptionWhere the issue happened: [kernel moved from 3.14 to 4.4] auron auron_paine auron_yuna buddy gandof guado jecht lulu rikku samus tidus veyron_fievel veyron_gus veyron_jaq veyron_jerry veyron_mickey veyron_mighty veyron_minnie veyron_pinky veyron_speedy veyron_thea veyron_tiger What the issue was: autoupdate_EndToEndTest.paygen_au_canary_full failed and the DUTs were no longer pingable after the failure of udpate_stateful(). This issue is caused by enabling the encryption on file system where the devices need power wash to wipe stateful. Since some devices were moved from kernel 3.14 to 4.4 where 3.14 doesn't support encryption feature but 4.4 does. The move happened during M54.
,
Jun 6 2017
,
Jun 6 2017
Wow, that's a lot of boards. Far more than I expected. This move happened during R54. Do we believe that this would be globally fixed if we move the stepping stone up for R54 and stop testing R53 on any device?
,
Jun 6 2017
,
Jun 6 2017
Technically the boards above aren't being move to v4.4. Gwendal landed changes in chromeos-3.14 to support the new encryption in M54.
,
Jun 6 2017
Re comment #3: I would think yes, the issue would go away if the stepping stone is M54.
,
Jun 6 2017
Right, these devices are not moved to 4.4
,
Jun 6 2017
I guess we can move stepping stone to M54 but we just recently set to M53 but I guess no other alternative here?
,
Jun 6 2017
In this case, we can move it instead of creating an additional one. The alternative is to harden provision/end to end test against these problems, but that has proven really hard.
,
Jun 7 2017
Can the stepping stone be by BOARD? See 730141.
,
Jun 7 2017
Looking again, the stepping stone at R53 is fine. The problem is the inability for autoupdate_EndToEndTest to install stateful.tgz. See: https://bugs.chromium.org/p/chromium/issues/detail?id=689105#c72
,
Jun 8 2017
Issue should be addressed by 527422, see https://bugs.chromium.org/p/chromium/issues/detail?id=689105#c88
,
Jun 8 2017
,
Jun 8 2017
,
Jun 8 2017
Upgrading using 61 -> 53 -> 61 works: I have been using: test_that chromeos4-row9-rack10-host14.cros autoupdate_EndToEndTest \ --args="name=paygen_au_canary update_type=full source_release=8530.96.0 target_release=9626.0.0 target_payload_uri=gs://chromeos-releases/canary-channel/veyron-minnie/9626.0.0/payloads/chromeos_9626.0.0_veyron-minnie_canary-channel_full_test.bin-a0a75a8a50f8881b7e5e34058afd1796 SUITE=paygen_au_canary source_payload_uri=gs://chromeos-releases/stable-channel/veyron-minnie/8530.96.0/payloads/chromeos_8530.96.0_veyron-minnie_stable-channel_full_test.bin-00998204c6b61dd5f07c2a01a33b9858 source_archive_uri=gs://chromeos-releases/stable-channel/veyron-minnie/8530.96.0" \ --ssh_private_key ~/.ssh/chromium ~/.ssh/testing_rsa However, within the test, login_LoginSuccess fails: "Could not enable ARC via autotest API. "TypeError: Cannot read property 'getPlayStoreState' of undefined" [results-1-autoupdate_EndToEndTest/autoupdate_EndToEndTest.paygen_au_canary_full/status.log enclosed, as well as autoupdate_EndToEndTest.paygen_au_canary_full.DEBUG] The client.0.DEBUG file is overwritten by the next loginSuccess job, need to add tag somehow. This is expected as R53 does not support android, but we are using the latest login_LoginSuccess.py, Also, powerwashing takes > 8 minutes on veyron, very close to the 600s timeout. On slower machine, we may hit the timeout.
,
Jun 9 2017
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
ChromeOS Infra P1 Bugscrub. Issue untouched in a week after previous message. Downgrading to P2.
,
Sep 19 2017
This was fixed as part of the AU Test rewrite
,
Sep 19 2017
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 Deleted