Failed to load SELinux policy ????

[Brian Millett]

Ok, so I've never had selinux enabled.  The config is

__BEGIN__
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#	enforcing - SELinux security policy is enforced.
#	permissive - SELinux prints warnings instead of enforcing.
#	disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
#	targeted - Only targeted network daemons are protected.
#	strict - Full SELinux protection.
SELINUXTYPE=targeted
__END__

I've got selinux=0 as a boot arg,

so why am I getting this message at boot time??

"Failed to load SELinux policy."

Just started after the update to

Updated: selinux-policy-3.9.16-10.fc15.noarch
Updated: selinux-policy-targeted-3.9.16-10.fc15.noarch


thanks.
-- 
Brian Millett - [ Sinclair (re: The Line), "The Gathering"]
"The sky was full of stars and every star an exploding ship...one of ours."

[Phil Meyer]

On 04/04/2011 09:14 AM, Brian Millett wrote:
>  Ok, so I've never had selinux enabled.  The config is
>
>  __BEGIN__
>  # This file controls the state of SELinux on the system.
>  # SELINUX= can take one of these three values:
>  #	enforcing - SELinux security policy is enforced.
>  #	permissive - SELinux prints warnings instead of enforcing.
>  #	disabled - SELinux is fully disabled.
>  SELINUX=disabled
>  # SELINUXTYPE= type of policy in use. Possible values are:
>  #	targeted - Only targeted network daemons are protected.
>  #	strict - Full SELinux protection.
>  SELINUXTYPE=targeted
>  __END__
>
>  I've got selinux=0 as a boot arg,
>
>  so why am I getting this message at boot time??
>
>  "Failed to load SELinux policy."
>
>  Just started after the update to
>
>  Updated: selinux-policy-3.9.16-10.fc15.noarch
>  Updated: selinux-policy-targeted-3.9.16-10.fc15.noarch
>
>
>  thanks. 
Seeing the same thing here.  Had to add selinux=0 to the boot line to 
get it to boot at all.

[Steven Haigh]

On 04/05/2011 03:09 AM, Phil Meyer wrote:
>  On 04/04/2011 09:14 AM, Brian Millett wrote:
> > Ok, so I've never had selinux enabled.  The config is
> >
> > __BEGIN__
> > # This file controls the state of SELinux on the system.
> > # SELINUX= can take one of these three values:
> > #	enforcing - SELinux security policy is enforced.
> > #	permissive - SELinux prints warnings instead of enforcing.
> > #	disabled - SELinux is fully disabled.
> > SELINUX=disabled
> > # SELINUXTYPE= type of policy in use. Possible values are:
> > #	targeted - Only targeted network daemons are protected.
> > #	strict - Full SELinux protection.
> > SELINUXTYPE=targeted
> > __END__
> >
> > I've got selinux=0 as a boot arg,
> >
> > so why am I getting this message at boot time??
> >
> > "Failed to load SELinux policy."
> >
> > Just started after the update to
> >
> > Updated: selinux-policy-3.9.16-10.fc15.noarch
> > Updated: selinux-policy-targeted-3.9.16-10.fc15.noarch
> >
> >
> > thanks.
>  Seeing the same thing here.  Had to add selinux=0 to the boot line to
>  get it to boot at all. 
We're just discussing this in #fedora-qa...

https://bugzilla.redhat.com/show_bug.cgi?id=693410

-- 
Steven Haigh

Email: netwiz(a)crc.id.au
Web: http://www.crc.id.au
Phone: [phone]
Fax: [phone]

[Brian Millett]

On Tue, 2011-04-05 at 03:27 +1000, Steven Haigh wrote:
>  We're just discussing this in #fedora-qa...
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=693410  
Thanks,

CC'd to that bug.  Now, patience my young padawan.

There is another bug, but it has to deal with relabeling of the
filesystem.  Since I've never had selinux enabled, that can't be it.
-- 
Brian Millett - [ Delenn and Sinclair, "The Gathering"]
"Why Babylon 5? If the prior four stations were lost or destroyed, why
    build another?"
'Plain old human stubbornness I guess. When something we value is destroyed,
    we rebuild it. If its destroyed again, we rebuild it again...and again
    and again and...again. Until it stays. That as our poet Tennison once
    said is the goal: to strive, to seek, to find, and not to yield.'