Bug 1321638

Description of problem:

During the RHEL 7.2 kickstart installation, anaconda installer will not take special crashkernel parameter into account. 
e.g 'bootloader --location=mbr --append="crashkernel=512M-2G:64M,2G-:128M"'

And the resulted system will have 'crashkernel=auto' in '/proc/cmdline'. Also kdump service will be in failed status.

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

How reproducible:
100%, 'crashkernel=512M-2G:64M,2G-:128M' parameter will not taken into account by anaconda installer 

Steps to Reproduce:
1. install RHEL 7.2 using below kickstart file:

~~~~~~
[root@kickstart pub]# egrep -v "^$|^#" rhel7.cfg 
lang en_US
graphical
cdrom
keyboard us
network  --bootproto=dhcp --device=eth0
timezone America/New_York --isUtc
rootpw redhat
bootloader --append="rhgb quiet crashkernel=512M-2G:64M,2G-:128M" --location=mbr --boot-drive=sda --driveorder=sda
zerombr
clearpart --all --initlabel
autopart
auth --passalgo=sha512 --useshadow
selinux --enforcing
firewall --disabled
firstboot --disable
%packages
@base
@gnome-desktop
@input-methods
@legacy-x
@remote-desktop-clients
@fonts
@desktop-debugging
@x11
%end
~~~~~~


Actual results: 

- installed system should take crashkernel value as mentioned in the kickstart file but it takes 'auto' instead 

- outputs from reproducer system:

~~~
[root@localhost ~]# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet LANG=en_US.UTF-8

[root@localhost ~]# egrep -v "^$|^#" /etc/kdump.conf
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31

[root@localhost ~]# systemctl status kdump.service 
● kdump.service - Crash recovery kernel arming
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2016-03-28 22:06:59 IST; 2h 2min ago
  Process: 983 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE)
 Main PID: 983 (code=exited, status=1/FAILURE)

Mar 28 22:06:59 localhost.localdomain dracut[3858]: drwxr-xr-x   2 root     root            0 Mar 28 22:06 var/lib/lldpad
Mar 28 22:06:59 localhost.localdomain dracut[3858]: lrwxrwxrwx   1 root     root           11 Mar 28 22:06 var/lock -> ../run/lock
Mar 28 22:06:59 localhost.localdomain dracut[3858]: lrwxrwxrwx   1 root     root            6 Mar 28 22:06 var/run -> ../run
Mar 28 22:06:59 localhost.localdomain dracut[3858]: ========================================================================
Mar 28 22:06:59 localhost.localdomain kdumpctl[983]: No memory reserved for crash kernel.
Mar 28 22:06:59 localhost.localdomain kdumpctl[983]: Starting kdump: [FAILED]
Mar 28 22:06:59 localhost.localdomain systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE
Mar 28 22:06:59 localhost.localdomain systemd[1]: Failed to start Crash recovery kernel arming.
Mar 28 22:06:59 localhost.localdomain systemd[1]: Unit kdump.service entered failed state.
Mar 28 22:06:59 localhost.localdomain systemd[1]: kdump.service failed.
~~~


Expected results:

- installed system should take crashkernel value as 'crashkernel=512M-2G:64M,2G-:128M'


Additional info:

Attaching installation logs from reproducer system