Red Hat Bugzilla – Bug 469854
Selecting [Back] then [Next] at Package selection screen clears out all default selected packages
Last modified: 2013-09-02 02:29:05 EDT
Created attachment 322426 [details]
Description of problem:
Manually select *all* package groups. Somehow selinux is not installed on the system and the system cannot boot after install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot installer
2. Proceed to graphical package selection
3. Manually select every package group (right-side of package selection)
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
type=1404 audit(....): enforcing=1 old_enforcing=0 auid=.... ses=...
SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.23: No such file or directory
Unable to load SELinux policy (No such file or directory). Halting now
A boot able system with selinux installed
* See attached log files
* See attached boot screenshot
* Able to boot the system by passing "selinux=0"
Created attachment 322427 [details]
Created attachment 322428 [details]
Created attachment 322429 [details]
Created attachment 322430 [details]
Bingo ... why/how did selinux-policy-targeted get added to the exclude list?
# grep selinux-policy /root/anaconda-ks.cfg
If you are running with selinux you need to install a policy, you excluded the policy which causes the machine to not work.
No, the attached anaconda-ks.cfg was the one written out by anaconda after installation. selinux-policy-targeted is showing up as excluded there because of something anaconda (or hopefully some other package) did.
Created attachment 322446 [details]
Same steps followed on ppc F10-PreviewRelease and similar results found ... attaching anaconda-logs-ppc.tgz.
The commonality seems to be that a slew of packages are added to the exclude list somehow.
I remember you previously indicated that if you select all the groups, then hit back, then hit next to return to package selection, all the packages are removed. Is that what we're seeing here too?
Created attachment 322732 [details]
Retested now being careful *not* to hit [Back] then [Next] ... it appears to have done the right thing. selinux is properly installed.
I think it's safe to say this bug is specific to the default||optional package lists being cleared out when going [Back] then [Next] to the pkg selection screen.
Fixed in git
*** Bug 470495 has been marked as a duplicate of this bug. ***
This will be in rawhide as of 20081108 or later. Please re-test.
Re-tested with the anaconda just tagged and this is in fact fixed. Going back, and then going into customize now once again re-sets everything back to their default status.