yum error after fc2 t2 update

[Phil Moors]

On Fri, 2004-04-02 at 11:49, Paul Nasrat wrote:
> On Fri, Apr 02, 2004 at 11:04:20AM -0500, seth vidal wrote:
> 
> > > I can do a fresh install, is you would like me to try to duplicate this ????
> > > 
> > 
> > It sounds like a transaction was killed mid-stream by _something_ and
> > the only thing I can think of right now is enforcing mode.
> 
> I think the reproducer may be being staff_r not sysadm_r under enforcing when
> you run - certainly this post lends itself to that:
> 
> http://www.redhat.com/archives/fedora-selinux-list/2004-April/msg00036.html
> 
> Paul
> 

I just added the following comment to bug 119597:

Install from CD on 3-31 was okay. I got this same problem after doing
a yum update on 4-1 (about 150 packages). I believe a policy update
was in the mix.

I could only get into the failsafe session as root/staff_r. Had to
newrole -r sysadm_r to run as real root. setfiles /home didn't fix the
problem. Neither did fixfiles relabel (and reboot).

Looking in /etc/security/selinux I found a policy.15 file and a
policy.16 file. The policy.16 file was date stamped as the original
install from CD. The policy.15 file was date stamped March 24, which I
assume was time of packaging. I moved the policy.16 file to /root
leaving only file_contexts and policy.15 in the selinux directory.

When I went to logout gdm got caught in a loop trying to restart over
and over. A three-finger salute took the system down via init6.

After the reboot, the system is AOK. Login with home directory and
enforcement is on.

No scientific analysis was done here. I just "tried something" and it
worked.

Hope this helps.
Phil