Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 514534

Summary:	system-config-network gui assigns wrong DEVICE for virtual interfaces
Product:	Red Hat Enterprise Linux 5	Reporter:	Keith Sundberg <kssundberg>
Component:	system-config-network	Assignee:	Harald Hoyer <harald>
Status:	CLOSED ERRATA	QA Contact:	Branislav Blaškovič <bblaskov>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.3	CC:	lmiksik, pknirsch, psklenar
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When creating several device aliases for the same interfaces, the system-config-network service did not store the correct device name in the relevant configuration file. As a consequence, the interface was started with an incorrect interface name. With this update, system-config-network now correctly stores the device aliases and interfaces are named properly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-16 00:17:40 UTC	Type:	---
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:	1049888

Description Keith Sundberg 2009-07-29 15:01:33 UTC

Description of problem:

Found that editing an existing virtual interface causes the DEVICE setting to
be incorrect, usually changing it to eth0:0 no matter what the actual device is
supposed to be.

Version-Release number of selected component (if applicable):
? Could have existed since at least RHEL 5.1, possibly before.

How reproducible:
100%

Steps to Reproduce:
1. New install of RHEL 5.3 (RHEL 5.2 and CentOS show the same behavior)
2. Create eth0 with a statically assigned IP address using the system-config-network gui.
3. Add 1 virtual interface, eth0:1 with a fixed IP address.
4. Add 2nd virtual interface, eth0:2 with a fixed IP address.
5. Saved from the GUI.
6. Activate both devices at the GUI.

Both virtual interfaces showed up correctly in /etc/sysconfig/networking/devices/* and the files reflected the correct details for the "DEVICE" setting, eth0:1 and eth0:2.

7. Back to the GUI, I changed the setting on eth0:2 for "Activate this device when parent device starts" from checked to unchecked.
8. Saved from the GUI.
9. Attempted to activate from the GUI, but it failed.

Checked the file at /etc/sysconfig/networking/devices/ifcfg-eth0:2 which showed the incorrect setting: "DEVICE=eth0:0"

Actual results:
If you edit the device config in the GUI, it will always set the Device Alias Number in the Hardware Device tab to 0. This is even if you don't select the Hardware Device tab.

Expected results:
It should not change the Device Alias Number (DEVICE setting in /etc/sysconfig/networking/devices/*) unless the user inputs a change.

Additional info:

Comment 2 RHEL Program Management 2009-11-06 19:06:35 UTC

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 5 Branislav Blaškovič 2014-06-04 12:28:24 UTC

Thank you for detailed description. 

Your steps to reproduce works ok now.
# grep DEVICE /etc/sysconfig/networking/devices/ifcfg-eth0:2
DEVICE=eth0:2


Testing with system-config-network-1.3.99.23-1.el5.

Comment 7 errata-xmlrpc 2014-09-16 00:17:40 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.

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