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:
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 "?".
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.
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