[Canary] Failed at autoupdate_EndToEndTest.paygen_au_canary_full on devices which moved from 3.10 to 4.4 kernel |
|||||
Issue descriptionWhere the issue may happen: [kernel moved from 3.10 to 4.4] gnawty orco banjo hoofer ninja sumo candy heli swanky enguarde expresso quawks kip clapper glimmer squawks winky 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.10 to 4.4 where 3.10 doesn't support encryption feature while 4.4 does. The move happened during M57/M58. Gwendal is investigating and will update the bug.
,
Jun 7 2017
Testing on glimmer. I haven't found the root cause yet. 3.10 kernel it not crashing when presented a ext4 fs with encryption failure, it nicely reject the mount. I also verified e4crypt tool is failing nicely. However, the kernel crashes in loop at boot with a "attempted to kill init" kernel panic. I would have expected a rollback in the lab. Given glimmer moved to 4.4 1/17 and direncryption was added 3/17, a possible the stepping stone is in a narrow window.
,
Jun 8 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 is obsolete with the au test rewrite |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dgarr...@chromium.org
, Jun 6 2017