[Bug 1582325] Re: udf with --custom-tarball that is too big: cannot pass bootsplash on reboot

[Jean-Baptiste Lallement]

Thanks for your report. This is the same problem that happens on OTA
when someone installs additional packages in the system partition and
there is not enough space left to apply the OTA. It is a non recoverable
situation and there must be a protection against this in system-image.

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
       Status: New => Confirmed

** Also affects: system-image (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  udf with --custom-tarball that is too big: cannot pass bootsplash on
  reboot

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  New

Bug description:
  Summary: I am installing my own customized tarball to cooler with udf
  using --customized-tarball option. If the customized tarball is too
  large, udf reports "can't write" error and fails.

  Rebooting from recovery menu leaves device stuck in bootsplash.

  We don't want this to happen on a channel.

  Details to follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1582325/+subscriptions