Red Hat Bugzilla – Bug 291461
use of non-integer aliases causes system-config-network to dump a stack trace
Last modified: 2009-01-20 16:54:12 EST
Description of problem:
One of my developers changed the name of the alias he set up on his main
interface to something descriptive, calling it eth0:robot.
When I brought up system-config-network, it immediately crashed, complaining
about line 196 of /usr/share/system-config-network/netconfpkg/NCDevice.py.
If you look at this line, it tries to coerce the alias part of the interface
name into an int.
This is a problem if you have used a more descriptive name, like one that isn't
Version-Release number of selected component (if applicable):
Create an ifcfg-eth0:robot file in /etc/sysconfig/networking-scripts.
Restart network. Note that the interface is created just fine.
Bring up system-config.network, it will stack dump.
Reassigning to component owner.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This bug needs a review from the component owner before granting Devel ACK.
Read ya, Phil
Granting Devel ACK after review of the package maintainer
Read ya, Phil
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
* system-config-network is not capable of handling non-numerical aliases for network interfaces. Previously, if a user set one of these aliases to a non-numerical value, system-config-network would crash. This updated package shows the warning message instead of crashing.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.