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.
Description of problem: Determining IP information for eth0 ... interface name too long
Version-Release number of selected component (if applicable):
RHEL 6.9 Beta (Santiago)
How reproducible:Always
Steps to Reproduce:
1. Install RHEL6.9 Server.
2. Try to bring the eth0 interface up
Actual results:
Unable to obtain IP address from DHCP server and when the interface is shutdown and started again using ifup it gives the below message
"Determining IP Information for eth0 .../var/run/dhclient-eth0.pid: interface name too long (is 26)
This version of ISC DHCP is based on the release available on ftp.isc.org. Feature have been added and other changes have been made to the base software release in order to make it work better with this distribution
Please report for this software via the RedHat bugzilla site http://bugzilla.redhat.com exiting. failed.
Unable to obtain IPv4 DHCP address eth0
RTNETLINK answers: File exists.
Expected results:
Additional info:
Version:
cat /etc/redhat-release
Red Hat Enterprise Linux Client release 6.9 Beta (Santiago)
kernel-2.6.32-671.el6.x86_64
dhcp-common-4.1.1-53.P1.el6.x86_64
Build: RHEL-6.9-20161121.n.0
===cat /var/log/messages===
Nov 22 07:45:14 client /etc/sysconfig/network-scripts/ifup-eth: Unable to obtain IPv4 DHCP address eth0
Nov 22 07:45:14 client dhclient[2338]: /var/run/dhclient-eth0.pid: interface name too long (is 26)
Nov 22 07:45:14 client dhclient[2338]:
Nov 22 07:45:14 client dhclient[2338]: This version of ISC DHCP is based on the release available.
Nov 22 07:45:14 client dhclient[2338]: on ftp.isc.org. Features have been added and other changes.
Nov 22 07:45:14 client dhclient[2338]: have been made to the base software release in order to make
Nov 22 07:45:14 client dhclient[2338]: it work better with this distribution.
Nov 22 07:45:14 client dhclient[2338]:
Nov 22 07:45:14 client dhclient[2338]: Please report for this software via the Red Hat Bugzilla site
Nov 22 07:45:14 client dhclient[2338]: http://bugzilla.redhat.com
Nov 22 07:45:14 client dhclient[2338]:
Nov 22 07:45:14 client dhclient[2338]: exiting.
Nov 22 07:45:14 client /etc/sysconfig/network-scripts/ifup-eth: Unable to obtain IPv4 DHCP address eth0
Thank you for reporting this.
First of all the bug should be reported against initscripts or reproduced with using of dchlient only.
The bug was reported against beta version of software and most likely fixed in initscript version released.
I'm closing the bug because of leak of data to analyze. Please reproduce the issue with stable version and reopen the bug with proper component if needed.