Removing linux-image-extra-X-generic deletes initramfs

This happened with linux-image-extra-3.13.0-36-generic 3.13.0-36.63 but the code in postrm is also present in the latest utopic kernel.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1375310

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

No need for logs, it's easy to reproduce.

This bug was fixed in the package linux - 3.16.0-21.28

---------------
linux (3.16.0-21.28) utopic; urgency=low

  [ Andy Whitcroft ]

  * [Config] linux-image-extra is additive to linux-image
    - LP: #1375310
  * [Config] linux-image-extra postrm is not needed on purge

  [ dann frazier ]

  * [Config] run updateconfigs after adding arm64 PCI support
  * SAUCE: (no-up) Fix pcie-xgene build failure

  [ Ming Lei ]

  * SAUCE: (no-up) apm: pcie: fix hang when no card connected

  [ Tanmay Inamdar ]

  * SAUCE: (no-up) arm64: PCI(e) arch support
  * SAUCE: (no-up) pci: APM X-Gene PCIe controller driver
  * SAUCE: (no-up) arm64: dts: APM X-Gene PCIe device tree nodes
  * SAUCE: (no-up) dt-bindings: pci: xgene pcie device tree bindings
  * SAUCE: (no-up) MAINTAINERS: entry for APM X-Gene PCIe host driver
  * SAUCE: (no-up) Add MSI/MSI-X driver for APM PCI bus
    - LP: #1318977

  [ Tim Gardner ]

  * rebase to v3.16.4
  * Release Tracking Bug
    - LP: #1377905

  [ Tuan Phan ]

  * SAUCE: (no-up) pci-xgene-msi: fixed deadlock in irq_set_affinity
    - LP: #1359514

  [ Upstream Kernel Changes ]

  * drm/nouveau: make sure display hardware is reinitialised on runtime
    resume
    - LP: #1374607

  [ Upstream Kernel Changes ]

  * rebase to v3.16.4
 -- Tim Gardner <email address hidden> Fri, 03 Oct 2014 12:10:48 -0400

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I can confirm that removing linux-image-extra keeps the inintramfs image intact now.

This bug was fixed in the package linux - 3.13.0-39.66

---------------
linux (3.13.0-39.66) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1386629

  [ Upstream Kernel Changes ]

  * KVM: x86: Check non-canonical addresses upon WRMSR
    - LP: #1384539
    - CVE-2014-3610
  * KVM: x86: Prevent host from panicking on shared MSR writes.
    - LP: #1384539
    - CVE-2014-3610
  * KVM: x86: Improve thread safety in pit
    - LP: #1384540
    - CVE-2014-3611
  * KVM: x86: Fix wrong masking on relative jump/call
    - LP: #1384545
    - CVE-2014-3647
  * KVM: x86: Warn if guest virtual address space is not 48-bits
    - LP: #1384545
    - CVE-2014-3647
  * KVM: x86: Emulator fixes for eip canonical checks on near branches
    - LP: #1384545
    - CVE-2014-3647
  * KVM: x86: emulating descriptor load misses long-mode case
    - LP: #1384545
    - CVE-2014-3647
  * KVM: x86: Handle errors when RIP is set during far jumps
    - LP: #1384545
    - CVE-2014-3647
  * kvm: vmx: handle invvpid vm exit gracefully
    - LP: #1384544
    - CVE-2014-3646
  * Input: synaptics - gate forcepad support by DMI check
    - LP: #1381815

linux (3.13.0-38.65) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1379244

  [ Andy Whitcroft ]

  * Revert "SAUCE: scsi: hyper-v storsvc switch up to SPC-3"
    - LP: #1354397
  * [Config] linux-image-extra is additive to linux-image
    - LP: #1375310
  * [Config] linux-image-extra postrm is not needed on purge
    - LP: #1375310

  [ Upstream Kernel Changes ]

  * Revert "KVM: x86: Increase the number of fixed MTRR regs to 10"
    - LP: #1377564
  * Revert "USB: option,zte_ev: move most ZTE CDMA devices to zte_ev"
    - LP: #1377564
  * aufs: bugfix, stop calling security_mmap_file() again
    - LP: #1371316
  * ipvs: fix ipv6 hook registration for local replies
    - LP: #1349768
  * Drivers: add blist flags
    - LP: #1354397
  * sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O timeout
    - LP: #1354397
  * drm/i915/bdw: Add 42ms delay for IPS disable
    - LP: #1374389
  * drm/i915: add null render states for gen6, gen7 and gen8
    - LP: #1374389
  * drm/i915/bdw: 3D_CHICKEN3 has write mask bits
    - LP: #1374389
  * drm/i915/bdw: Disable idle DOP clock gating
    - LP: #1374389
  * drm/i915: call lpt_init_clock_gating on BDW too
    - LP: #1374389
  * drm/i915: shuffle panel code
    - LP: #1374389
  * drm/i915: extract backlight minimum brightness from VBT
    - LP: #1374389
  * drm/i915: respect the VBT minimum backlight brightness
    - LP: #1374389
  * drm/i915/bdw: Apply workarounds in render ring init function
    - LP: #1374389
  * drm/i915/bdw: Cleanup pre prod workarounds
    - LP: #1374389
  * drm/i915: Replace hardcoded cacheline size with macro
    - LP: #1374389
  * drm/i915: Refactor Broadwell PIPE_CONTROL emission into a helper.
    - LP: #1374389
  * drm/i915: Add the WaCsStallBeforeStateCacheInvalidate:bdw workaround.
    - LP: #1374389
  * drm/i915/bdw: Remove BDW preproduction W/As until C stepping.
    - LP: #1374389
  * mptfusion: enable no_write_same for vmware scsi disks
    - LP: #1371591
  * iommu/amd: Fix cleanup_domai...

The fix of running all the kernel-post-install hooks on removal of a linux-image-extra package causes another bug (#1440608) with the autoremoval feature. Please see my comment on https://bugs.launchpad.net/bugs/1440608 .

@ Andy Whitcroft:
- in the commit d7235802d7735e53936c5ccfbe9e071021b394fb you write regarding linux-image-extra:
"As it also depends on linux-image we know that linux-image will have been installed before it, and will be removed after it."
The last part is not correct. We have no way of knowing, if the linux-image will be removed as well. Please see https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/comments/37 for a more detailed reasoning.

Since all we need on installation and removal of linux-image-extras is a rebuild of the corresponding version of the initrd, I would say this is all we should do. And not abuse and run all of the kernel post-install hooks on both occasions. At least on my systems I don't see any good reason to run any of the other hooks.

Please see the attached patch for the postinst and postrm hooks for the -extra package.

Regards,
Robert.