Comment 19 for bug 2028366

I suppose it's possible that the particular dkms module that failed to build is essential for booting the system, so the new approach that hides this build failure could render the system unbootable without the user realizing it. A bit less catastrophic, but still very serious, would be for the machine to lose network access (wifi driver), which could pose a chicken an egg problem (need network to fix the problem).

So what we have here is a balance between a system with an interrupted release-upgrade, requiring a lot of apt-foo to fix, or a system where dkms rebuilds might have failed, but otherwise upgraded successfully. Both cases could result in an unbootable system, but I tend to agree that the first one (interrupted release-upgrade) is more likely to be much harder to recover (been there).

I would like some sort of commitment on the follow-up work for the release upgrader to check the status of dkms builds after the upgrade. Can we get an LP bug for it please?