Bug 694620

Summary: SELinux blocking boot after latest update - was disabled.
Product: [Fedora] Fedora Reporter: Mariusz Smykuła <mariuszs>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-08 21:57:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
boot error screen none

Description Mariusz Smykuła 2011-04-07 19:15:02 UTC
Created attachment 490621 [details]
boot error screen

Description of problem:

After update (2-3 april) and restart I cannot boot to system. I has disabled selinux.

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

Fedora15Alpha, updated

How reproducible:

Always

Steps to Reproduce:
1. Boot to fedora
2. Stop on boot animation

  
Actual results:

Logs on boot console

Failed to load SELinux policy.
Failed to set security context system_u:object_r:var_run_t:s0 for /run: Invalid argument
Failed to set security context system_u:object_r:sysfs_t:s0 for /run: Invalid argument
Failed to set security context system_u:object_r:sysfs_t:s0 for /run: Invalid argument
Faile to mount /sys/fs/cgriup/systemd: No such file or directory
_

Expected results:

Boot to GDM screen

Additional info:

Please help me, how to repair system? I have tried enabling selinux and single mode and this not help me.

Comment 1 Daniel Walsh 2011-04-08 18:18:05 UTC
This has been fixed.  You need to update libselinux, systemd, selinux-policy, udev to the latest build from updates-testing

Comment 2 Mariusz Smykuła 2011-04-08 18:30:10 UTC
Ok, thanks. I need to use Fedora Rescue and chroot to system?

Comment 3 Daniel Walsh 2011-04-08 19:51:38 UTC
You can probably boot with the enforcing=0 flag.

Comment 4 Mariusz Smykuła 2011-04-08 20:13:12 UTC
This not work, I have selinux disabled already.

Comment 5 Mariusz Smykuła 2011-04-08 21:07:55 UTC
I can chroot to FC15 form my stable FC14, but without network access. What rpm file I should download and install to fix selinux issues?

Comment 6 Mariusz Smykuła 2011-04-08 21:57:35 UTC
OK, updated from chroot and boot again.

Comment 7 Mariusz Smykuła 2011-04-08 22:21:06 UTC
I have to enable relabeling on boot to fix this...