Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1196085

Summary: Kdump over network requires DNS1 variable set
Product: Red Hat Enterprise Linux 7 Reporter: Zdenek Pytela <zpytela>
Component: kexec-toolsAssignee: Minfei Huang <mhuang>
Status: CLOSED ERRATA QA Contact: Qiao Zhao <qzhao>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: jherrman, mhuang, nbansal, ruyang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kexec-tools-2.0.7-27.el7 Doc Type: Bug Fix
Doc Text:
Due to incorrect DNS settings in the /etc/resolv.conf file, automatic network uploads of the vmcore dump file previously failed. This update modifies /etc/resolv.conf to allow DNS resolving to work properly. As a result, kdump now uploads the vmcore file successfully.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 03:46:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1133060, 1205790    

Description Zdenek Pytela 2015-02-25 09:38:10 UTC 
Description of problem:

Kdump over network requires DNS1 variable set in interface config file to have name resolving working. /etc/resolv.conf is not copied to initramfs. Configuration is static, NM is not used.

Version-Release number of selected component (if applicable):
kexec-tools-2.0.4-32.el7_0.5.x86_64    
dracut-033-161.el7_0.173.x86_64                             


How reproducible:
always


Steps to Reproduce:
1. Set up /etc/kdump.conf with
ssh kdump@FQDN
2. Properly set interface with BOOTPROTO=static and no DNS lines, set /etc/resolv.conf
3. Start kdump service
4. Crash the kernel


Actual results:
Vmcore is not uploaded as DNS resolving does not work


Expected results:
Vmcore is uploaded


Additional info:  
Adding DNS1= file into ifcfg file makes the service working.
Comment 4 Minfei Huang 2015-04-14 09:48:38 UTC 
(In reply to Zdenek Pytela from comment #0)
> Description of problem:
> 
> Kdump over network requires DNS1 variable set in interface config file to
> have name resolving working. /etc/resolv.conf is not copied to initramfs.
> Configuration is static, NM is not used.
> 
> Version-Release number of selected component (if applicable):
> kexec-tools-2.0.4-32.el7_0.5.x86_64    
> dracut-033-161.el7_0.173.x86_64                             
> 
> 
> How reproducible:
> always
> 
> 
> Steps to Reproduce:
> 1. Set up /etc/kdump.conf with
> ssh kdump@FQDN
> 2. Properly set interface with BOOTPROTO=static and no DNS lines, set
> /etc/resolv.conf

Why did you set the config to the /etc/resolv.conf, not to the interface config file? If so, kdump will work well.

Thanks
Minfei

> 3. Start kdump service
> 4. Crash the kernel
> 
> 
> Actual results:
> Vmcore is not uploaded as DNS resolving does not work
> 
> 
> Expected results:
> Vmcore is uploaded
> 
> 
> Additional info:  
> Adding DNS1= file into ifcfg file makes the service working.
Comment 5 Zdenek Pytela 2015-04-28 12:18:26 UTC 
Customer decided to use resolv.conf for domain name resolution. This is perfectly valid. We would like to have kdump working with this configuration.
Comment 6 Minfei Huang 2015-05-13 02:24:38 UTC 
(In reply to Zdenek Pytela from comment #5)
> Customer decided to use resolv.conf for domain name resolution. This is
> perfectly valid. We would like to have kdump working with this configuration.

Hi, Zdenek.

I am curious that why the customer uses resolv.conf, instead of the interface configuration file. Also kdump can work if both resolv.conf and interface file are configured.

Thanks
Minfei
Comment 7 Zdenek Pytela 2015-06-04 12:21:55 UTC 
Customer has his own reasons - global deployment of the file (with puppet, but it's not important). Anyway, this approach is valid as resolv.conf can be a primary configuration file.
Comment 13 errata-xmlrpc 2015-11-19 03:46:41 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-2182.html