Red Hat Bugzilla – Bug 1257857
Configure kdump failed via NFS
Last modified: 2016-03-09 09:36:08 EST
Created attachment 1067944 [details]
Description of problem:
It reports error while configure kdump failed via NFS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install rhev-hypervisor7-7.1-20150827.1.el7ev
2. Enable network
3. Configure Kdump via NFS type
4. Check #mount
5. Check /etc/kdump.conf file
6. Check the TUI page.
1. After step3. it reports error as follows.
KDump configuration failed, location unreachable. Previous configuration was restored.
2. After step4, it nfs location which I filled is already mounted.
10.66.65.196:/home/huiwa/nfs2 on /run/kdump-nfs type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.66.10.46,local_lock=none,addr=10.66.65.196)
3. After step5, NFS location is not saved in /etc/kdump.conf file.
4. After step6, TUI still shows Local as Kdump type.
1. Kdump via NFS should be configured without error.
I can't reproduce this, and no changes have been made to the kdump code recently. Are you sure this isn't a problem with the environment?
Still can't reproduce this.
If it's reproducible, can you please let me know the details of a system I can check it on, and the appropriate kdump path?
It looks like I couldn't reproduce it (and QE didn't hit it earlier), because /var/crash already existed on my NFS share. If it doesn't, kdump now expects that users should create that manually...
Lowering the priority because it happens only if the target dir is missing, and thus only affecting really new installs with non-existent target dirs.
1. Install rhev-hypervisor7-7.2-20151025.0.el7ev
2. Enable network
3. From the remote NFS server, clean the target dir
4. Configure Kdump via NFS type
5. Check #mount
6. Check /etc/kdump.conf file
7. Check the TUI page.
1. Kdump can be setup as NFS type succeed.
So this issue is fixed in ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch. Change the status to Verified.
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.