Created attachment 560784 [details] secure Description of problem: install with vnc, vnc conconnect or vnc password and minimal packages, after click reboot button on the vncviewer, the system does not reboot. by forcing power off and reboot the system, cannot login system with root. boot system with init 1 and change the root password, still cannot login it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install with vnc 2. power off 3. boot system Actual results: cannot login Expected results: login normally Additional info:
Created attachment 560785 [details] install log
Created attachment 560786 [details] install log syslog
Created attachment 560787 [details] anaconda syslog
Created attachment 560788 [details] anaconda log
Created attachment 560789 [details] program log
Created attachment 560790 [details] storage log
Created attachment 560791 [details] druct log
Created attachment 560792 [details] audit log
reproduced with minimal packages installation
set it as F17 Alpha Blocker according F17 Alpha Release Criteria article: "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles"
This is not a regression in PAM as it did not change recently. Looking into the audit.log attached by you I see that the SELinux contexts are seriously messed up. I suppose it might be caused by the UsrMove change.
(In reply to comment #11) > This is not a regression in PAM as it did not change recently. Looking into the > audit.log attached by you I see that the SELinux contexts are seriously messed > up. I suppose it might be caused by the UsrMove change. (In reply to comment #11) > This is not a regression in PAM as it did not change recently. Looking into the > audit.log attached by you I see that the SELinux contexts are seriously messed > up. I suppose it might be caused by the UsrMove change. yeah, after I set the selinux to permissive, it can be logged in.
Could you try to relabel your system $ touch /.autorelabel;reboot and see if this resolves your issue.
Ok, I got the same issue if I built my own live image. I am going to test it with the latest policy.
Looks like it happens also on update.
If it is mislabeled then there is something going wrong in livecd builder. In the last step of the livecd-tools it is supposed to fix all the labels, is this failing? Do you see anything in the logs of livecd build?
To be clear, is this a problem with the livecd booting or the system installed from livecd booting? Also, if you could test with the TC2 image so that everyone is on the same page that would be good. Self-built images could be pulling wrong packages, untested updates, etc. etc.
Could this be the same as my https://bugzilla.redhat.com/show_bug.cgi?id=788829 ? Same symptom - 'can't log in' - and apparently the same cause - 'SELinux contexts are seriously messed up'. I think we need to know what the hell keeps 'seriously messing up' the SELinux contexts. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Discussed at the 2012-02-10 blocker review meeting. Agreed we're concerned there's something wiggy going on with SELinux contexts in current Rawhide and this may well be related to 788829, but we'd like a clearer understanding of what's going on before we declare this to be a blocker. We'd also like to know what image Hongqing installed from - Hongqing, was this TC1? TC2? DVD? netinst? We will revisit this bug at the 2012-02-17 blocker review meeting.
Hongqing was using TC2 as indicated by the TC1 and TC2 install test pages - the only references to this bug are on the TC2 page. I also saw this on TC2 but not TC1. (I got a working minimal install on one of the TC2 DVDs which showed this bug. I didn't get a working install with the other DVD. With TC1, I got working minimal installs from both DVDs and neither had this problem.)
It should be the same with bug 788829. It also cannog be logged in with graphical mode. *** This bug has been marked as a duplicate of bug 788829 ***