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
