Bug 165378
Summary: | Problems with RPM when SELinux is disabled | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Blanchard <fedora> |
Component: | libselinux | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | nobody+pnasrat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-02 17:55:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andy Blanchard
2005-08-08 18:12:36 UTC
The values permitted for seloinux variables are clearly documented in the file, and none of the permitted values are null. I know that a null string is not a permitted value. I initially installed SELinux with FC3, didn't have time to get it working properly and so disabled it, but left the policy configured as "targeted" intending to get back to it but never got around to it. The problem is that when upgrading from FC3 to FC4 with SELinux configured as above something in the upgrade process sets the value to a null string, hence the error messages after the reboot. This is why my original suggestion was that a solution might be to ensure that a value is set for "SELINUXTYPE" when installing/upgrading the policy packages, even if "SELINUX" is set to disabled. Uninstalling, removing the config file and then re-installing the two policy packages does seem to create a valid file, so the issue may be specific to whatever RPM installation method Anaconda is using during an upgrade. This is a selinux configuration, not an rpm, problem. Changing component. |