Image got in a broken state after update -> rollback -> update (wrong kernel)

Bug #1474125 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Fix Released
High
Unassigned
15.04
Fix Released
Critical
Sergio Schvezov

Bug Description

Testing with stable image, but the bug should also show up with rolling.

Flashed alpha 3 (kernel 3.19.0-18-generic), updated and booted to image 4 (3.19.0-22-generic), did a rollback to 3, and then did an update to 4 again. After trying to reboot the system (to get it to boot into image 4 again) it couldn't boot it properly because the kernel used when booting image 4 was actually the one available in image 3 (it failed when mounting the boot partition, because it couldn't find the right module, since the kernel was the wrong one).

$ sudo ubuntu-device-flash --revision 3 core 15.04 --channel alpha --oem beagleblack --enable-ssh --developer-mode --install webdm --output beagle.img

Related branches

description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

As discussed and shown, the problem is that SyncBootloaderFiles is run regardless and the system-image-cli may not download any delta as it is already on the latest according to it's RunInOther.

I have a potential non invasive fix in mind which I will apply tonight.

Revision history for this message
Michael Vogt (mvo) wrote :

So just to clarify, we have two problems here:
- fatwrite causes file system corruption
- after rollback the subsequent upgrade override the previous kernnel via SyncBootloaderFiles()

Leo Arias (elopio)
no longer affects: snappy/trunk
Revision history for this message
Michael Vogt (mvo) wrote :

No more SyncBootloaderFiles() in ubuntu core 16 :-D

Changed in snappy:
assignee: Sergio Schvezov (sergiusens) → nobody
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.