clr-boot-manager doesn't remove old Clear kernels when booted in a custom kernel

[cmarcelo]

When clr-boot-manager update is called (manually or as part of swupd update) while the machine is running a custom kernel (not the ones provided by Clear), it seems to exit before it can clear up old kernels. Would be nice if it still could remove older kernels.

By default Clear keeps the running and the latest. Perhaps in this case that the running kernel is not from Clear, it could keep the two latest ones provided by Clear.

Note: I'm considering cbm will never remove a custom kernel -- which I think is the correct behavior.

[cmarcelo]

@bryteise @dorileo

[bryteise]

Ideally we would want to keep the last known booting kernel (of each type, this can quickly eat up a fair amount of space in the EFI partition as a warning to maybe not keep a ton of kernel types installed).

[cmarcelo]

In my case, I might stay a few updates without booting a Clear kernel. When I do, it does make sense to me to also have the "latest from Clear" which isn't necessarily the "last known booting".

[bryteise]

Ah sorry I wasn't clear at all X(. We always keep the latest kernel but usually that is the same as the last known good kernel. In this case there will likely be two different kernels which is why I commented about the EFI space.

[seanvk]

https://github.com/clearlinux/clr-boot-manager/issues/194 is also a related issue on the fact that you cannot even install another kernel when running a custom kernel.

[ahkok]

transferred the issue - highly specific to CBM.

[dorileo]

Thank you @cmarcelo cbm shouldn't fail in that case, I'll take a look at that. Thanks.

[tuzhms]

I have the same problem. I delete old kernels manually when filling the /boot partition