[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: initramfs-tools-ubuntu-core (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Released Status in initramfs-tools-ubuntu-core source package in Artful: Won't Fix Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This bug was fixed in the package initramfs-tools - 0.125ubuntu12.1 --- initramfs-tools (0.125ubuntu12.1) artful; urgency=medium [ Oliver Grawert ] * make fixrtc catch "n/a" string and fall back to a sane value for the date command instead (LP: #1623125) -- Michael Vogt Fri, 05 Jan 2018 10:23:22 +0100 ** Changed in: initramfs-tools (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Released Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.11 --- initramfs-tools (0.122ubuntu8.11) xenial; urgency=medium [ Oliver Grawert ] * make fixrtc catch "n/a" string and fall back to a sane value for the date command instead (LP: #1623125) -- Michael Vogt Wed, 20 Dec 2017 09:38:07 +0100 ** Changed in: initramfs-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Released Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
Since there is no possible way of testing this for artful, I assume the sanity-test performed by Oliver is enough. Also, the package has been in artful-proposed since 75 days and no regressions have been reported. Unblocking. ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Released Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Branch linked: lp:~xnox/britney/custom-kernels-cannot-pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
I have verified the xenial one with a locally created core and kernel snap now (as mentioned before I can not verify it on artful simply because there is no Ubuntu Core for this release, using the deb from proposed on an artful desktop does not show any regressions though) ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This SRU has gone 49 days without verification, and at this point looks like it will miss the window for 16.04.4. Will someone from the Snappy team be verifying this so that it can be included in future core snaps and ubuntu-core images? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
Hello Oliver, or anyone else affected, Accepted initramfs-tools into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.125ubuntu12.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: initramfs-tools (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: initramfs-tools-ubuntu-core (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful ** Changed in: initramfs-tools (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
I uploaded updates for zesty and artful now as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
It is like ogra said - the snapd team does not care about zesty/artful, but if it makes the SRU easier we are happy to push to zesty/artful as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
Yes, I will work on this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
since we dont build ubuntu core images based on the artful archive this would just be cosmetic ... (but yeah, technically we could also upload it to artful ... xenial and bionic are the critical ones here though) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
Shouldn't this also be fixed in Artful? I'm not concerned about Zesty since its EoL is imminent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This bug was fixed in the package initramfs-tools - 0.125ubuntu13 --- initramfs-tools (0.125ubuntu13) bionic; urgency=medium [ Oliver Grawert ] * make fixrtc catch "n/a" string and fall back to a sane value for the date command instead (LP: #1623125) -- Michael Vogt Wed, 20 Dec 2017 09:44:43 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Changed in: snappy Status: Triaged => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Triaged => Confirmed ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** 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 Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Triaged Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Triaged Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: New Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Triaged Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Triaged Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp