Bug 90420
Summary: | redhat-config-network crashes immediately after opening | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <k.y.rozier> | ||||||||||||
Component: | redhat-config-network | Assignee: | Harald Hoyer <harald> | ||||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | medium | ||||||||||||||
Version: | 7.3 | ||||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | i686 | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2003-05-15 10:35:22 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: | |||||||||||||||
Attachments: |
|
Description
Need Real Name
2003-05-07 23:06:29 UTC
Created attachment 91545 [details]
Dump
which version is this? $ rpm -q redhat-config-network will find out. Have you upgraded to the latest erratum via RHN or ftp? The version is: redhat-config-network-1.0.0-1 Yes, the latest erratum had been applied via RHN the day before I encountered this bug. for 7.3 there is a 1.0.4-2 erratum available.. Created attachment 91583 [details]
Second error dump
I've upgraded to redhat-config-network-1.0.4-2 (sidenote: Why didn't this update happen with a plain 'up2date'? I had to do an 'up2date redhat-config-network' afterwards.) Unfortunately, this didn't correct the behavior of the application. The new error message dump is attached. please attach /etc/sysconfig/networking/devices/ifcfg-eth0 Created attachment 91586 [details]
/etc/sysconfig/networking/devices/ifcfg-eth0
Here is the file you requested.
I am puzzled... could you please remove the last duplicate line of ifcfg-eth0 with an editor and insert a newline instead and retry? Never saw this error... or just remove all IPX lines if you can? I have removed all of the IPX lines from the /etc/sysconfig/networking/devices/ifcfg-eth0 file. I still get exactly the same error. there is a newline missing at the end of your file... just add an empty line at the end and the problem should be gone. I will consider this in my next bugfix. Unfortunately, I cannot seem to just add an empty line at the end of this file. Every time I try adding an empty line and saving it, the next time I run "redhat-config-network" it acts just the same -- crashing with the error message attached earlier. When I re-open the file after that, I find that my change (the addition of the newline) has been deleted. How do I prevent this from happening? Created attachment 91623 [details]
Conf.py
copy Conf.py to /usr/share/redhat-config-network/netconfpkg/Conf.py
can you please try out the Conf.py which should bugfix your version I copied over the new Conf.py file. Now I get this error: % redhat-config-network Traceback (innermost last): File "/usr/sbin/neat", line 49, in ? from netconfpkg import * File "/usr/sbin/../share/redhat-config-network/netconfpkg/__init__.py", line 40, in ? exec cmd File "<string>", line 1, in ? File "/usr/sbin/../share/redhat-config-network/netconfpkg/Conf.py", line 157, in ? from log import log ImportError: No module named log Created attachment 91640 [details]
log.py
copy to the same place as Conf.py
Now a call to "redhat-config-network" results in a message: "Copying ifcfg-eth0 to devices and putting it into the default profile" and the opening of the network configuration GUI. I still suspect that the "redhat-config-network" tool may not be operating as optimally as perhaps it should be. (For example I now have an "eth0.old" inactive device which still seems to be listed as having "Active" status even though the "Activate" button is active and the "Deactivate" one is not.) However, the bug that is the subject of this bug report appears to be fixed -- the utility opens successfully and allows me to modify the network configuration. Thanks for your help! |