Description of problem:

/etc/kdump.conf has a comment that 'default halt' will halt the system, regardless of the success or failure of vmcore capture:
 
[root@el7a ~]# less /etc/kdump.conf
...
# default <reboot | halt | poweroff | shell | dump_to_rootfs>
...
#                         halt:   If the default action is halt, then simply
#                                 halt the system after attempting to capture
#                                 a vmcore, regardless of success or failure.

This conflicts with the kdump.conf man page, which says 'default' specifies the 'Action  to  preform in case dumping to intended target fails':

[root@el7a ~]# man kdump.conf
...
       default <reboot | halt | poweroff | shell | dump_to_rootfs>
              Action  to  preform in case dumping to intended target fails. If no default action is specified, "reboot" is assumed default.  reboot: If the default action is reboot simply reboot the system (this is what most people will want, as it returns the system to a nominal state).  shell: If the default action is shell, then  drop  to  an shell session inside the initramfs from where you can manually preform additional recovery actions.  Exiting this shell reboots the system.  halt: bring the system to a halt, requiring manual reset poweroff: The system will be powered down. dump_to_rootfs:If the default action is dump_to_rootfs, specified root will be  mounted  and dump will be saved in "path" directory.  Note: kdump uses bash as the default shell.

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

[root@el7a ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.2 (Maipo)

[root@el7a ~]# rpm -q kexec-tools
kexec-tools-2.0.7-38.el7.x86_64

Additional info:

Also lots of typos in /etc/kdump.conf and man kdump.conf (e.g. 'preform', 'an shell')