Bug 75063 – traceback, if no /etc/cipe

Bug 75063 - traceback, if no /etc/cipe

Summary:	traceback, if no /etc/cipe

Status:	CLOSED DUPLICATE of bug 74873

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	redhat-config-network (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i686 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Harald Hoyer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-10-03 23:04 EDT by Mark Cooke
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Mark Cooke 2002-10-03 23:04:53 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
The config tool crashes after the user has spent a while setting up the cipe
interface details because /etc/cipe does not exist unless the cipe rpm is installed.

Only when 'applying' changes in the interface list screen causes the crash.

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


How reproducible:
Always

Steps to Reproduce:
1.Default workstation install
2.Attempt to setup a cipe VPN without installing cipe rpm first
3.Attempt to save new interface details.
	

Actual Results:  CIPE Interface setup is lost as the tool crashes because
/etc/cipe doesn't exist.

Expected Results:  The tool should have created /etc/cipe, and warned that cipe
rpm was not available.

Additional info:

Comment 1 Harald Hoyer 2003-01-13 06:57:57 EST


*** This bug has been marked as a duplicate of 74873 ***

Comment 2 Red Hat Bugzilla 2006-02-21 13:49:44 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.