Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 78863 - Conf.py:936:__setitem__
Status: CLOSED DUPLICATE of bug 71171
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-12-02 09:27 EST by Brad Potter
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Network Config Crash using Graphical Config (1.14 KB, text/plain)
2002-12-02 09:28 EST, Brad Potter
no flags Details

  None (edit)
Description Brad Potter 2002-12-02 09:27:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020501

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Change Networking component using NEAT in Network Configuration
2.Apply Changes
3.Network Config Crashes

Actual Results:  Network Configuration Graphical Interface closes with changes
not being applied

Expected Results:  Network Configuration applied

Additional info:
Comment 1 Brad Potter 2002-12-02 09:28:51 EST
Created attachment 87029 [details]
Network Config Crash using Graphical Config
Comment 2 Phil Knirsch 2002-12-10 11:51:34 EST
Reassigned to correct component.

Read ya, Phil
Comment 3 Harald Hoyer 2003-03-25 05:24:26 EST
Did the latest redhat-config-network update from RHN fix your problem?
Comment 4 Harald Hoyer 2003-05-21 12:29:55 EDT

*** This bug has been marked as a duplicate of 71171 ***
Comment 5 Red Hat Bugzilla 2006-02-21 13:50:15 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.