Created attachment 395292 [details]
/var/log/secure shows failures in root login.
Description of problem:
After bug 566948 stymied graphical install, tried installation with
basic video driver. This generated complaints about missing dependencies for:
Chose to continue installation. 179 packages installed.
After installation completed, and subsequent reboot, could not login
as root. Rebooted to runlevel 1 successfully, and found in /var/syslog/messages:
Feb 20 13:57:18 localhost init: tty (/dev/tty1) main process ended, respawning
Feb 20 13:57:57 localhost init: tty (/dev/tty1) main process ended, respawning
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from alpha-RC1 DVD
2. Select "install with basic video driver"
Dependency failure messages during installation; unable to login
Correct packages on install media.
Successful login as root.
The following files are available:
but they say nothing about failed dependencies.
I encountered the same problem with anaconda 13.28 and it was 100% reproducible.
The images I tested are at:
Set it as F13 alpha blocker bug according to Alpha Release Requirements: 2. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install and (for root login issue) maybe 12. In most cases, the installed system must boot to a functional (graphical) environment.
Please attach all the anaconda log files to this bug so we can see what's going on. Thanks.
Created attachment 395361 [details]
Created attachment 395362 [details]
Created attachment 395364 [details]
Created attachment 395365 [details]
Created attachment 395366 [details]
Created attachment 395367 [details]
Looks like the underlying problem is that system-config-firewall-base is not included in the install media, therefore we can't install it and run lokkit to configure the machine for logging in:
13:47:01,285 DEBUG anaconda: no package matching system-config-firewall-base
13:54:26,197 ERROR anaconda: Error running /usr/sbin/lokkit: No such file or directory
this appears to be a problem with pungi during the compose. Looking into it now.
This could have been a yum problem, or just a problem with the state of the repos at the time, but I cannot duplicate it at this point.
Verified fixed in F13 alpha RC2.