Bug 903989 – The second time kdump will failed and report "kdump NFS location cannot be empty" if choose kdump to NFS first time.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 903989 - The second time kdump will failed and report "kdump NFS location cannot be empty" if choose kdump to NFS first time.

Summary:	The second time kdump will failed and report "kdump NFS location cannot be em...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	ovirt-node (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	x86_64 Unspecified

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Fabian Deutsch
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:	913688
	Show dependency tree / graph

Reported:	2013-01-25 03:48 EST by cshao
Modified:	2014-01-21 14:20 EST (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Previously every error message which appeared on the kdump page was not discarded after it was shown, so error messages were repeated even if when they did not apply. Now, kdump error messages are discarded after they are shown.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-01-21 14:20:00 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
ovirt.log (104.97 KB, text/plain) 2013-01-25 03:49 EST, cshao	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2014:0033	normal	SHIPPED_LIVE	ovirt-node bug fix and enhancement update	2014-01-21 19:14:30 EST

Groups: None (edit)

Description cshao 2013-01-25 03:48:06 EST

Description of problem:
The second time kdump will failed and report "kdump NFS location cannot be empty" if choose kdump to NFS first time.
But can successful from SSH remote access.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130116.3.0.el6

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H and configure network.
2. Choose kdump to NFS.
3. Press F2 enter cmd, run command  "echo c > /proc/sysrq-trigger"
4. After reboot, choose kdump to NFS or ssh or local again.
  
Actual results:
1. The second time kdump will failed and report "kdump NFS/SSH location cannot be empty" 
2. SSH to this host and kdump can successful.

Expected results:
Kdump always can successful.

Additional info:
No such issue on rhev-hypervisor6-6.4-20121212.1.el6, so it is a regression bug.

Comment 1 cshao 2013-01-25 03:49:21 EST

Created attachment 687331 [details]
ovirt.log

Comment 3 haiyang,dong 2013-01-25 05:08:11 EST

Met the similar problem as follow steps:
1. Install RHEV-H and configure network.
2. Configure kdump via NFS ,don't input nfs info, and click "Apply" Button.
3. Then configure kdump via Restore(Local), click "Apply" Button.

After step 2, it will prompt that "KDump NFS location cannot be empty", it's expected behavior.
But after step 3, it still prompt that "KDump NFS location cannot be empty",
this wasn't expected behavior to user.

Comment 4 Fabian Deutsch 2013-01-28 04:27:32 EST

http://gerrit.ovirt.org/11450

Tested as follows:
1. Apply patch
2. On the KDUMP page, select NFS with no location and hit apply
3. Kdump NFS error is shown "KDump NFS location cannot be empty"
4. Hit ok
5. Select Restore (Local) and hit apply
6. Kdump configuration is restored

Comment 11 cshao 2013-10-25 01:18:51 EDT

Test version:
rhev-hypervisor6-6.5-20131017.0
ovirt-node-3.0.1-4.el6.noarch

Test steps:
1. Install RHEV-H and configure network.
2. Choose kdump to NFS.
3. Press F2 enter cmd, run command  "echo c > /proc/sysrq-trigger"
4. After reboot, choose kdump to NFS or ssh or local again.

Test result:
Kdump always can successful.

So the bug is fixed, change bug status to VERIFIED.

Comment 13 errata-xmlrpc 2014-01-21 14:20:00 EST

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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html

Note You need to log in before you can comment on or make changes to this bug.