[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command

[Alfonso Sanchez-Beato]

** Description changed:

  The fixrtc script is failing with message:
  
  date: invalid date '          Wed Apr  1 17:23:44 2020'
  
  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs -h'
  ouptput, and some clean-up on it happens, but it looks like it is not
  enough for BusyBox' date command, at least for the version in focal.
+ 
+ [Impact]
+ 
+ The system date shown on first boot is incorrect, which can be
+ problematic on first boot if at that point in time there is no network
+ connection. If fixrtc works correctly at least we get the date of the
+ last time the rootfs was mounted, which is modern enough to avoid
+ problems with snap assertions validation, etc.
+ 
+ [Test case]
+ 
+ Boot an image with fixrtc in the kernel command line in a system with no
+ network. snap seeding will fail without the patch.
+ 
+ [Regression Potential]
+ 
+ Quite small, as the fix is small and targeted.

** Description changed:

  The fixrtc script is failing with message:
  
  date: invalid date '          Wed Apr  1 17:23:44 2020'
  
  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs -h'
  ouptput, and some clean-up on it happens, but it looks like it is not
  enough for BusyBox' date command, at least for the version in focal.
+ 
+ Backporting this to focal is needed.
  
  [Impact]
  
  The system date shown on first boot is incorrect, which can be
  problematic on first boot if at that point in time there is no network
  connection. If fixrtc works correctly at least we get the date of the
  last time the rootfs was mounted, which is modern enough to avoid
  problems with snap assertions validation, etc.
  
  [Test case]
  
  Boot an image with fixrtc in the kernel command line in a system with no
  network. snap seeding will fail without the patch.
  
  [Regression Potential]
  
  Quite small, as the fix is small and targeted.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1880968

Title:
  fixrtc fails due to bad format of input to the date command

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The fixrtc script is failing with message:

  date: invalid date '          Wed Apr  1 17:23:44 2020'

  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs
  -h' ouptput, and some clean-up on it happens, but it looks like it is
  not enough for BusyBox' date command, at least for the version in
  focal.

  Backporting this to focal is needed.

  [Impact]

  The system date shown on first boot is incorrect, which can be
  problematic on first boot if at that point in time there is no network
  connection. If fixrtc works correctly at least we get the date of the
  last time the rootfs was mounted, which is modern enough to avoid
  problems with snap assertions validation, etc.

  [Test case]

  Boot an image with fixrtc in the kernel command line in a system with
  no network. snap seeding will fail without the patch.

  [Regression Potential]

  Quite small, as the fix is small and targeted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions