kdump-tools does not have an upstart job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
makedumpfile (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Louis Bouchard |
Bug Description
[SRU justification]
The upstart job avoids the sysVinit scripts to be run while kdump-tools is doing the kernel crash dump capture
[Impact]
Potential impossibility to capture a kernel crash dump
[Fix]
Add kdump-tools.conf upstart job
[Test Case]
With the upstart job, the kdump-tools kernel dump capture will run before any of the tasks triggered by RUNLEVEL [2345] will run.
[Regression]
Minimal; The job uses the same syntax as the sysVinit job currently in use.
[Original description of the problem]
kdump-tools relies on a sysVinit script to capture the kernel dump. It sometimes gets interference from other jobs starting at runlevels 2 to 5.
An upstart job starting before RUNLEVEL is emitted would alleviate that.
Changed in makedumpfile (Ubuntu Trusty): | |
status: | Confirmed → In Progress |
description: | updated |
tags: | added: sts |
Marking dev release as invalid since it relies on systemd