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.
trying to boot a new dragonboard image results in:
error: assertion is signed with expired public key "-CvQKAwRQ5h3Ff n10FILJoEZUXOv6 km9FwA80- Rcj-f-6jadQ89VR swHNiEB9Lxk" 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.