Bug 115542 (TB38693268)
Summary: | maindialog.py:270:changed:AttributeError: mainDialog | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | grammarsoft <grammarsoft> |
Component: | redhat-config-network | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED NEXTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
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: | 2006-08-04 20:31:54 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: |
Description
grammarsoft
2004-02-13 13:32:31 UTC
Created attachment 97643 [details]
Bug log created after crash of network config
Component: redhat-config-network Version: 1.2.0 Summary: TB38693268 maindialog.py:270:changed:AttributeError: mainDialog instance has no attribute 'active_profile_name' Traceback (most recent call last): File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 1003, in on_hostnameEntry_changed File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 335, in checkApply File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 270, in changed AttributeError: mainDialog instance has no attribute 'active_profile_name' change in /etc/sysconfig/network: CURRENT_PROFILE=default and all should be ok. Red Hat Linux and Red Hat Powertools are currently no longer supported by Red Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED state for these products. However, we do want to make sure that nothing important slips through the cracks. If, in fact, these issues are not resolved in a current Fedora Core Release (such as Fedora Core 5), please open a new issues stating so. Thanks. |