failed to rollback from 15.04 alpha #4 to #3
Bug #1474126 reported by
Leo Arias
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Critical
|
Oliver Grawert |
Bug Description
I flashed snappy 15.04 alpha #3 in my beaglebone black. Today there's a new image on that channel, so I updated.
I rebooted and got into alpha #4. Then I tried to rollback to #3, but after the reboot, it fails to boot and I end up in #4 again. So it's no possible for me to rollback.
My test log with the steps to reproduce: http://
This is the serial console after the reboot: http://
Changed in snappy: | |
milestone: | none → 15.04.2 |
assignee: | nobody → Oliver Grawert (ogra) |
Changed in snappy: | |
status: | In Progress → Fix Committed |
Changed in snappy: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
(BeagleBoneBlac k)ubuntu@ localhost: /boot/uboot$ ls -l a/
total 19616
drwxr-xr-x 2 root root 512 Jul 13 16:02 dtbs
-rwxr-xr-x 1 root root 114 Jul 13 16:02 hardware.yaml
-rwxr-xr-x 1 root root 13574238 Jul 13 16:02 initrd.img
-rwxr-xr-x 1 root root 6510264 Jul 13 16:02 vmlinuz
(BeagleBoneBlac k)ubuntu@ localhost: /boot/uboot$ md5sum a/vmlinuz a2c2e998aab1c0b cc a/vmlinuz k)ubuntu@ localhost: /boot/uboot$ md5sum a/initrd.img 8813a3f718b24f7 77 a/initrd.img k)ubuntu@ localhost: /boot/uboot$ sudo md5sum /boot/vmlinuz- 3.19.0- 18-generic a2c2e998aab1c0b cc /boot/vmlinuz- 3.19.0- 18-generic k)ubuntu@ localhost: /boot/uboot$ md5sum /boot/initrd. img-3.19. 0-18-generic 8813a3f718b24f7 77 /boot/initrd. img-3.19. 0-18-generic
baae473daca1d9f
(BeagleBoneBlac
c42761096016a6a
(BeagleBoneBlac
baae473daca1d9f
(BeagleBoneBlac
c42761096016a6a
After updating to image 4 and booting again: k)ubuntu@ localhost: /boot/uboot$ ls -l a/ k)ubuntu@ localhost: /boot/uboot$ md5sum a/VMLINUZ eb9055ffde9c9c5 ec a/VMLINUZ k)ubuntu@ localhost: /boot/uboot$ md5sum a/INITRD.IMG 51d6de9ab520635 af a/INITRD.IMG
(BeagleBoneBlac
total 19616
drwxr-xr-x 2 root root 512 Jul 13 16:02 DTBS
-rwxr-xr-x 1 root root 114 Jul 13 16:02 HARDWA~1.YAM
-rwxr-xr-x 1 root root 13574238 Jul 13 16:02 INITRD.IMG
-rwxr-xr-x 1 root root 6510264 Jul 13 16:02 VMLINUZ
(BeagleBoneBlac
26e74d8bbae82f6
(BeagleBoneBlac
f52e6affb217282
So it did end up modifying the kernel (maybe via fsck?).