Hide Forgot
Created attachment 832440 [details] attached Screenshot for kdump_using_ssh_mode Description of problem: When configured Kdump with "nfs" mode, it reports as the follows. An error occurred KDump configuration failed, location unreachable.Previous configuration war restored Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.3-1.1.fc19.iso ovirt-node-3.0.3-1.1.fc19.noarch How reproducible: 100% Steps to Reproduce: 1. Install ovirt-node-upstream, configure network up 2. Configure Kdump with "nfs" mode. 3. Focus on the promot info. Actual results: It will report "location unreachable" . And configuration will not be successful. Expected results: Host can be configured with "SSH" mode successfully. Additional info:
Is this with nfs or ssh? Both are referenced.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Could you take a look at Ryan's comment 1 ?
(In reply to Fabian Deutsch from comment #3) > Could you take a look at Ryan's comment 1 ? It only failed Configure Kdump with "nfs" mode.Host can be configured with "SSH" mode successfully.
Ok. Is this reproducable with all current Node images, or are there specific steps I need to take to reproduce?
(In reply to Ryan Barry from comment #5) > Ok. > > Is this reproducable with all current Node images, or are there specific > steps I need to take to reproduce? i couldn't find 3.0.4 iso that depends on Fedora 19 building, so i used http://resources.ovirt.org/releases/3.4/iso/ovirt-node-iso-3.4-20140423.0.el6.iso to check, couldn't reproduce it with 3.0.4 iso that depends on centos6 building. so maybe this bug only reproduce on ovirt-node iso that depends on Fedora 19 building.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
This should have been fixed with: https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=32e8cbc1c91ada764ef4b5bb817b0c045d3fb3a4 Please re-open if it's still reproducable on current images.