Re: [rhelv5-list] SELinux re-enabled after 5.2 Upgrade

Joe Kazura Fri, 14 Nov 2008 09:23:59 -0800

Tom:

I AGREE COMPLETELY!!!

I have just spent the last WEEK trying to figure out MULTIPLE issues with a RHEL 5.0 server that over time became 5.2 ...

The whole POINT of the ENTERPRISE Linux is that the OS has been THOUROGHLY tested by both RH & the Fedora community.

One of my regular desktops is Core 9 and has been WAAAAY more stable than this RHEL 5.x system.

A recent kernel update (2.6.18-92.1.17.el5 ... from 2.6.18-92.1.13.el5) and a restart left the machine (Dell PE6650 which boots slow enough to begin with) un-bootable.

Reverting back to the last working kernel, 2.6.18-92.1.13.el5, left MANY things broken because of other updates.

Long story abbreviated, download 5.2 ISOs, upgrade install, removal of generically installed CRAP (it's a server! bluez-utils, irda-utils, wireless-tools) nuked HUGE pieces of the CORE OS! and left it in some half-mutant, mangled state!


And YES, 'selinux' was re-enabled!

  Joe 'the frustrated' ...


On Nov 14, 2008, at 10:23 AM, Tom Sightler wrote:

On Fri, 2008-11-14 at 10:35 +0000, solarflow99 wrote:

       the same happened here in october.

       clean fresh 5.0, not registered, only for testing, no updates
       for
       several months, no problems, selinux=disabled
       rhn_register ;  yum update -> 5.2, oops,  selinux=enforcing

       thanks at redhat for the extra time to solve the problems via
       ssh :(

it cant be that hard to figure out, a quick look at the logs would
show all sorts of AVC messages


It might not be hard to figure out, but it can be a total pain.  We've
had different failure states with this problem.  In some cases the

system wouldn't even boot. Fortunately almost of our systems have some

time of remote management, but for the ones that didn't, that meant

scheduling a physical visit to the machine. Others booted, but wouldn't

allow SSH because SSH logins were being denied by SElinux.

Having the system silently change my selected security options reflects

poorly on the quality of the Redhat upgrade process and can't be

dismissed because of the "it can't be that hard to figure out" argument.

It shouldn't be that hard for Redhat not to change my settings, and a
point upgrade should certainly keep my existing options.

Anyway, it's good to know others have experienced this issue as well.

Sounds like I should open a support case/bugzilla so that they can look

into the issue.

Later,
Tom



_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Re: [rhelv5-list] SELinux re-enabled after 5.2 Upgrade

Reply via email to