** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: initramfs-tools-ubuntu-core (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [TEST CASE]
+ * this will be tested by the snappy team
+ * without this fix the dragonboard will not boot on a freshly written image
+
+
trying to boot a new dragonboard image results in:
error: assertion is signed with expired public key
"-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
canonical
this is due to a clock skew that should normally be catched by the
fixrtc script in the initrd.
the script is supposed to check the last mount time of the writable disk
(SD card) and if this does not exist, fall back to the filesystem
creation time ...
in former versions of mkfs.ext4 the last mount time filed was simply
left empty, so this fallback worked fine ... in xenial the fields now
look like:
Filesystem created: Tue Sep 13 17:32:20 2016
Last mount time: n/a
Last write time: Tue Sep 13 17:32:20 2016
due to the script running with "set -e" it falls over on the "n/a" and
exists before falling back to creation time, there needs to be a check
added for the "n/a" string now.
** Description changed:
[TEST CASE]
* this will be tested by the snappy team
* without this fix the dragonboard will not boot on a freshly written image
+ [REGRESSION POTENTIAL]
+ * low as it only fixes an invalid string
trying to boot a new dragonboard image results in:
error: assertion is signed with expired public key
"-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
canonical
this is due to a clock skew that should normally be catched by the
fixrtc script in the initrd.
the script is supposed to check the last mount time of the writable disk
(SD card) and if this does not exist, fall back to the filesystem
creation time ...
in former versions of mkfs.ext4 the last mount time filed was simply
left empty, so this fallback worked fine ... in xenial the fields now
look like:
Filesystem created: Tue Sep 13 17:32:20 2016
Last mount time: n/a
Last write time: Tue Sep 13 17:32:20 2016
due to the script running with "set -e" it falls over on the "n/a" and
exists before falling back to creation time, there needs to be a check
added for the "n/a" string now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623125
Title:
fixrtc script does not catch "Last mount time: n/a" string
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
