Bug 105998 - kickstart.cfg omits port list for firewall
kickstart.cfg omits port list for firewall
Status: CLOSED DUPLICATE of bug 105994
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-10-01 17:15 EDT by John Reiser
Modified: 2007-11-30 17:10 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:58:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/root/anaconda-ks.cfg (1.35 KB, text/plain)
2003-10-01 17:16 EDT, John Reiser
no flags Details

  None (edit)
Description John Reiser 2003-10-01 17:15:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
After a new install, /root/anaconda-ks.cfg does not contain the list of open
ports that were selected for the firewall during security configuration.  The
kickstart just has "firewall --enabled\n" and does not specify that SSH (port
22) should be open, even though that was selected during the install.

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

How reproducible:

Steps to Reproduce:
1. New install Fedora Core Test 2 with ananconda Update Image 1.0 [README Sep 29
2. On the security configuration page, check the SSH box.  "Enable firewall" is
already checked; leave it checked.
3. Inspect /root/ananconda-ks.cfg after install finishes.

Actual Results:  "firewall --enabled" is the only listing.  Port 22 does not appear.

Expected Results:  SSH (port 22) should appear in a port list in the generated
kickstart file.

Additional info:
Comment 1 John Reiser 2003-10-01 17:16:20 EDT
Created attachment 94851 [details]

kickstart file generated by anaconda; omits port 22 (SSH) from firewall
configuration information, even though SSH was enabled during the install
Comment 2 Jeremy Katz 2003-10-16 14:42:47 EDT

*** This bug has been marked as a duplicate of 105994 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:58:52 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.