Bug 75858 - TB cipeconfig:191:updateRemoteOptions
TB cipeconfig:191:updateRemoteOptions
Status: CLOSED DUPLICATE of bug 75009
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: 81720
  Show dependency treegraph
Reported: 2002-10-14 00:42 EDT by Mark Cooke
Modified: 2008-05-01 11:38 EDT (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Mark Cooke 2002-10-14 00:42:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Changing a CIPE device from 'None - Server mode' to tunnel thorugh device causes
the applet to crash.

I have 3 network cards, 1 ppp and 2 CIPE interfaces defined.

Traceback (most recent call last):
  File "/usr/sbin/../share/redhat-config-network/netconfpkg/gui/cipeconfig.py",
line 191, in updateRemoteOptions
    d = fields[0]
IndexError: list index out of range

Local variables in innermost frame:
fields: []
self: <netconfpkg.gui.cipeconfig.cipeConfigDialog instance at 0x8504c84>
args: (<gtk.Entry object (GtkEntry) at 0x852ab24>,)
[root@sage mpc]# rpm -qf

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

How reproducible:

Steps to Reproduce:
1.Open network configuration panel
2.Select CIPE interface for configuration
3.Change tunnel settings from 'None' to 'Through Device'

Actual Results:  Applet crashes with index out of range error.

Expected Results:  The tunnel device should be changed.

Additional info:
Comment 1 Harald Hoyer 2003-01-13 09:37:10 EST

*** This bug has been marked as a duplicate of 75009 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:49:56 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.