Bug 1446688

Summary:	Bail out earlier in case of no reserved memory
Product:	Red Hat Enterprise Linux 7	Reporter:	Xunlei Pang <xlpang>
Component:	kexec-tools	Assignee:	Xunlei Pang <xlpang>
Status:	CLOSED ERRATA	QA Contact:	Emma Wu <xiawu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	dyoung, kdump-team-bugs, linl, lwang, piliu, ruyang, xiliang, xlpang, ymao
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	kexec-tools-2.0.14-9.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 09:33:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Xunlei Pang 2017-04-28 15:25:01 UTC

Description of problem:
Amazon EC2 C5 cloud complained that VM boot speed is slower than Ubuntu and other distributions, after some debugging, people found that one of the causes is kdump service starts slow, although it is parallel, it affects the speed more or less especially on VMs with few cpus, which is unacceptable.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Remove "crashkernel=X"
2. touch /etc/kdump.conf
3. date; kdumpctl start; date (see the elapsed seconds)

Actual results:
kdump service takes a few seconds to finish and fail.
Even more at the first time, because the new kdump initramfs is generated, then kdump service start fail.

Expected results:
bail out eariler without building/checking any initramfs even at the first time.

Additional info:

Comment 6 errata-xmlrpc 2017-08-01 09:33:50 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2300