The following has be reported by IBM LTC: [perf][specsfs] [BETA] Exception error during network configuration Please fill in each of the sections below. Hardware Environment: 4-way SMP IBM 8682 Software Environment: RedHat AS 3.0 Beta1 Steps to Reproduce: 1. Install RHAS 3.0 B1 2. From KDE, select network settings, then network configuration 3. try to Edit or Delete a network device, e.g., eth0 or eth1 Actual Results: Exception occurred and message appeared suggesting this is a bug and it should be filed against redhat-config-network. Expected Results: No problem Additional Information: See the attached file dump. Component: redhat-config-network Version: 1.2.51 Summary: TBbaeb9edc NCDevice.py:113:getDialog:TypeError: exceptions must be strings, classes, or instances, not NotImplementedType Traceback (most recent call last): File "/usr/src/build/279148-noarch/install/usr/share/redhat-config-network/net confpkg/gui/maindialog.py", line 734, in on_editButton_clicked File "/usr/src/build/279148-noarch/install/usr/share/redhat-config-network/net confpkg/gui/maindialog.py", line 825, in on_deviceEditButton_clicked File "/usr/src/build/279148-noarch/install/usr/share/redhat-config-network/net confpkg/gui/maindialog.py", line 854, in editDevice File "/usr/src/build/279148-noarch/install/usr/share/redhat-config-network/net confpkg/NCDevice.py", line 113, in getDialog TypeError: exceptions must be strings, classes, or instances, not NotImplemented Type Local variables in innermost frame: self: Device.IP=9.3.192.202 Device.Type=Ethernet Device.Netmask=255.255.255.0 Device.BootProto=static Device.DeviceId=eth0 Device.Device=eth0 Device.Gateway=9.3.192.1
please attach the output of: # redhat-config-network-cmd and all /etc/sysconfig/network-scripts/ifcfg-* files
may be fixed with 1.2.54
Can you follow up with some more info, Glen?
changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ACCEPTED |CLOSED ------- Additional Comments From khoa.com 2005-02-20 16:54 EST ------- Closing this very old bug now, assuming that it has already been resolved. If not, please re-open this bug report. Thanks.