Bug 72406 - Unable to customize the firewall in kickstart
Summary: Unable to customize the firewall in kickstart
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-kickstart
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-23 15:28 UTC by Fred New
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-28 17:25:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Fred New 2002-08-23 15:28:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
Running redhat-config-kickstart, I have selected "High" and "Customize", but I 
am unable to put a check mark in any of the fields in "Allow incoming:"

Version-Release number of selected component (if applicable):
  redhat-config-kickstart-2.3.2-16

How reproducible:
Always

Steps to Reproduce:
1. In Gnome Hat -> System Tools -> Kickstart
2. Enter Root Password in the Basic Configuration
3. Select Firewall configuration, High, Cusomize
4. Try clicking checking "SSH" box.
	

Actual Results:  No checkmark appears.

Expected Results:  A checkmark should appear in the box.

Additional info:

Comment 1 Peter van Egdom 2002-08-27 21:35:07 UTC
I have noticed this problem also; not being able to select checkmarks in
the 'allow incoming' field of the "Firewall configuration" section of
"redhat-config-kickstart".

[root@localhost tmp]# rpm -qa |grep config-kicks
redhat-config-kickstart-2.3.2-17


Comment 2 Brent Fox 2002-08-28 01:31:13 UTC
Should be fixed in 2.3.3-1. 

QA, please verify.

Comment 3 Peter van Egdom 2003-02-27 23:34:08 UTC
Confirmed fixed on "redhat-config-kickstart-2.3.6-2" on Phoebe 8.0.94.
Thanks!

Comment 4 Brent Fox 2003-02-28 17:25:46 UTC
Glad to know it's working.  Resolving as "Rawhide".  Thanks for your report.


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