Description of problem: It's missing iptables config after using kickstart build for RHEL 5.7 Version-Release number of selected component (if applicable): system-config-securitylevel-tui Installing RHEL 5.7 using kickstart How reproducible: The iptables config file is missing after completing the installation while customer uses following options at kickstart file : ---- . . . . firewall --enabled --port=22:tcp ## open Firewall Ports for TSM firewall --enabled --port=1500:tcp firewall --enabled --port=1501:tcp firewall --enabled --port=1502:tcp authconfig --enableshadow --enablemd5 selinux --enforcing . . . . %packages . . . . -system-config-securitylevel-tui ---- Note that he excluded package system-config-securitylevel-tui here. And I have just mentioned important fireall related options from their kickstart file. Steps to Reproduce: 1. As described above. 2. Also when they specify "selinux --permissive" in the command section, but the machines comes up in enforcing mode. This may be another issue. 3. Actual results: It's missing iptables config after using kickstart build for RHEL 5.7 Expected results: Iptables config file will be present. Additional info: When they take out line "-system-config-securitylevel-tui" from kickstart file, it works as expected. In their own words : "I have identified the problem. We are excluding system-config-securitylevel-tui in our packages list. When I take out the "-system-config-securitylevel-tui" line, the firewall & selinux commands are no longer ignored. I consider this to be a bug." For more information we can check case#00517881 at sfdc. *** Also component "system-config-securitylevel-tui" should be listed in our bugzilla component list.
This is an installation issue, therefore I am assigning this to anaconda. There is no component system-config-securitylevel-tui, because system-config-securitylevel-tui is a sub package of the component system-config-securitylevel.
Thanks Thomas.
anaconda should enforce the installation of system-config-firewall-tui regardless of what you do in your kickstart file. Please attach /tmp/anaconda.log to this bug report so we can get some more context. Thanks.
No problem. I shall provide that file and update you.
Feel free to reopen this bug if you can provide the requested information.