Bug 834316
Summary: | rsyslog update crashes systems with older selinux-policy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Konstantin Ryabitsev <icon> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | dwalsh, ksrot, mmalik, ssnodgra, theinric |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-29 07:23:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Konstantin Ryabitsev
2012-06-21 14:22:21 UTC
This appears to be fixed in the latest policy release, but before you close this as "WORKSFORME", consider this: 1. Quite a few people, including us, only apply security patches to their systems (yum --security update-minimal). Since rsyslog is a security update and selinux-policy is bugfix update, this will result in a situation like we faced this morning. Perhaps it's worth always marking selinux-policy updates as security? Maybe it is also worth evaluating if the selinux-policy version update is a hard dep from rsyslog. if it is not maybe we need a requires selinux-policy >= somever in the pkg. that would allow yum --security to work properly. I just got hit by this today (last night actually) on a couple of systems, and I'm pretty sure every RHEL6 system in my infrastructure is in danger of hanging whenever this new version makes it to my local yum mirror. The severity on this one should be way above medium. Everyone running automatic updates that don't happen to include the new selinux policy could get into serious trouble because of this bug. By the way, I haven't been able to test this yet, but I think this bug is even more dangerous than Konstantin mentions. I suspect, from examining my systems, that even if you are updating the selinux-policy RPM in the same yum transaction as the rsyslog update, and rsyslog just happens to go first, you are still hosed. I had 3 systems getting an early batch of updates, two of them hung immediately after the rsyslog update and the 3rd was fine because the selinux RPM happened to get updated prior to rsyslog. No, that shouldn't happen -- rsyslog service is restarted after the whole transaction has been completed, so as long as the newer selinux-policy has been installed along with rsyslog, regardless of order, things should work right. You may be right - I have puppet doing some package updates, so even though puppet wanted to do them all at once, it may not have been using a single yum transaction for the whole set. But again, this illustrates the danger that this bug poses, even if you do mean to update the selinux policy. By the way, as long as we are documenting this problem the root bugfix in the new selinux policy that fixes the issue is bug 754455. Seth - I don't think you could add a dependency for selinux to rsyslog, because it doesn't actually require the package and would function fine if selinux was completely absent. You'd need a way of saying "IF selinux-policy is installed, THEN the version must be > X". I'm not sure if RPM can do that, and you don't want rsyslog forcing an selinux install. *** This bug has been marked as a duplicate of bug 754455 *** |