Description of problem:
Since 7.1 (kexec-tools-2.0.7-1.el7), kdump behavior changed.
Previously, set kdump.conf option "path"
('test' directory does not exist.)
start kdump service is ok.
But now, start kdump service will fail if 'test' directory does not exist.
Talk with developer, they said this is a correct change.
And this action is still different from RHEL6, so we need to illustrate this point in the RHEL7.1 document.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
In latest kdump of rhel7, in case no target is specified explicitly in /etc/kdump.conf, the behavior of path is changed, a check need be taken to see if any separate file system is mounted on any tier of 'path', and also to take the relevant action. Meanwhile different than that kdump need create the dir specified in "path" formerly if it does not exist, now change the behavior to be that ueser takes charge of the "path", make sure "path" has been created, especially when separate disk is mounted on this "path".
How about following. I think we want to talk about only directory creation behavior change at this point of time.
"In RHEL7, kdump expects directory where dump is being saved to be present otherwise kdump service will fail. This is different from RHEL6 behavior where directory will be automatically created if it is not present by kdump service."
Yeah, it's fine. Your description is clear enough. I had thought about giving more background knowledge. It seems not necessary, and your description is clear enough.
*** Bug 1168445 has been marked as a duplicate of this bug. ***
Miroslav, do you know who is the qe contact for this bug, 7.1 rc is near, we should cover it in 7.1 doc...