xenial/linux-cascade: 4.4.0-1062.67 snap-debs snap:cascade-kernel

[Stefan Bader]

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
issue: KSRU-9875
kernel-stable-master-bug: 2037518
phase: Complete
phase-changed: Wednesday, 25. October 2023 20:51 UTC
reason: {}
snap-name: cascade-kernel
variant: snap-debs
~~:
  clamps:
    parent: 4.4.0-1062.67
    self: 4.4.0-1062.67

[Devices Certification Bot (ce-certification-qa)]

Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/fqKHAtyk/8371-cascade-kernel-440-106267-158-latest

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being closed

[Paul Larson (pwlars)]

Actually... there might be a problem here. The tests ran fine, but a later test on this device tried to install the stable kernel (152) after the refresh to this one in beta (158) and it failed with this:
07:29:20 error: cannot perform the following tasks:
07:29:20 - Update assets from kernel "cascade-kernel" (152) (volume cascade-image is not compatible with disk /dev/mmcblk0: cannot find disk partition /dev/mmcblk0p3 (starting at 575668224) in gadget: disk partition "" offset 575668224 (549 MiB) is not in the valid gadget interval (min: 135266304 (129 MiB): max: 135266304 (129 MiB)))

I know that snapd has some kernel refresh issues with a different device, so I thought it might be related to the core also being in beta at the time it tried to revert. So I tried reverting core to the one in stable and it still fails, though I don't get the same message above. Instead, it just fails because it reverts across reboot. This was the log from the task:
Status Spawn Ready Summary
Done yesterday at 22:49 UTC yesterday at 23:07 UTC Ensure prerequisites for "cascade-kernel" are available
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Download snap "cascade-kernel" (152) from channel "latest/
stable"
Done yesterday at 22:49 UTC yesterday at 23:07 UTC Fetch and check assertions for snap "cascade-kernel" (152)
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Mount snap "cascade-kernel" (152)
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Run pre-refresh hook of "cascade-kernel" snap if present
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Stop snap "cascade-kernel" services
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Remove aliases for snap "cascade-kernel"
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Make current revision for snap "cascade-kernel" unavailabl
e
Done yesterday at 22:49 UTC yesterday at 23:07 UTC Update assets from kernel "cascade-kernel" (152)
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Copy snap "cascade-kernel" data
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Setup snap "cascade-kernel" (152) security profiles
Undone yesterday at 22:49 UTC yesterday at 23:07 UTC Make snap "cascade-kernel" (152) available to the system
Error yesterday at 22:49 UTC yesterday at 23:07 UTC Automatically connect eligible plugs and slots of snap "ca
scade-kernel"
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Set automatic aliases for snap "cascade-kernel"
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Setup snap "cascade-kernel" aliases
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Run post-refresh hook of "cascade-kernel" snap if present
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Start snap "cascade-kernel" (152) services
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Remove data for snap "cascade-kernel" (156)
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Remove snap "cascade-kernel" (156) from the system
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Clean up "cascade-kernel" (152) install
Hold yesterday at 22:49 UTC yesterday at 23:07 UTC Run...

[Paul Larson (pwlars)]

Ok, I talked to Alfonso yesterday and according to him, there's a salesforce ticket with details (I can't see this) but there is a known limitation with the newer cascade kernels that they cannot revert to earlier stable kernels. I was told by him that the OEM is aware of this and is ok with it. I did confirm that I can refresh from 159 to 158 though - I just can't revert to earlier ones like 152