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:
If there is IPADRR instead of IPADDR variable, everything is reported as completed properly while in fact interface does not get configured.
Version-Release number of selected component (if applicable):
initscripts-9.03.38-1.el6_4.1.x86_64
How reproducible:
Extremely easy
Steps to Reproduce:
1. Modify ifcfg-ethX file to contain typo in IPADDR variable name.
2. ifdown/ifup interface
Actual results:
[root@el6vm ~]# ifdown eth1
[root@el6vm ~]# ifup eth1
[root@el6vm ~]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 52:54:00:AF:FE:27
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3554 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:173528 (169.4 KiB) TX bytes:11318 (11.0 KiB)
Interrupt:11 Base address:0xc000
Expected results:
Warning/Error message that no IP is configured should be displayed.
Additional info:
Yes this behavior is annoying, but I can't imagine any way how to improve it. There is no parser for these files, they are just sourced by the ifup scripts, so we can't recognize syntax error in configuration. On the other side there are some setups where you don't use dynamic configuration, but you also don't want to assign a IP address (there is a comment directly in the code "# enable device without IP, useful for e.g. PPPoE").
Comment 3RHEL Program Management
2013-10-14 02:37:41 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Description of problem: If there is IPADRR instead of IPADDR variable, everything is reported as completed properly while in fact interface does not get configured. Version-Release number of selected component (if applicable): initscripts-9.03.38-1.el6_4.1.x86_64 How reproducible: Extremely easy Steps to Reproduce: 1. Modify ifcfg-ethX file to contain typo in IPADDR variable name. 2. ifdown/ifup interface Actual results: [root@el6vm ~]# ifdown eth1 [root@el6vm ~]# ifup eth1 [root@el6vm ~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 52:54:00:AF:FE:27 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:3554 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:173528 (169.4 KiB) TX bytes:11318 (11.0 KiB) Interrupt:11 Base address:0xc000 Expected results: Warning/Error message that no IP is configured should be displayed. Additional info: