Bug 702865 - Major selinux problem after upgrade fc13 to fc14
Summary: Major selinux problem after upgrade fc13 to fc14
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 14
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Ben Levenson
URL:
Whiteboard:
: 702793 702795 702796 702797 702798 702799 702800 702801 702802 706750 707090 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-07 19:47 UTC by Eddie Lania
Modified: 2011-07-12 05:17 UTC (History)
7 users (show)

Fixed In Version: selinux-policy-3.9.7-42.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 05:17:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output of "grep setroubleshoot /var/log/messages" (724.38 KB, text/plain)
2011-05-07 19:47 UTC, Eddie Lania
no flags Details
Logwatch of the problematic system (127.34 KB, text/plain)
2011-05-08 14:34 UTC, Eddie Lania
no flags Details

Description Eddie Lania 2011-05-07 19:47:38 UTC
Created attachment 497578 [details]
output of "grep setroubleshoot /var/log/messages"

Description of problem: I don't know what went wrong.

I updated my fedora 13 system to fedora 14.
Now I am having major problems with SELinux. (The upgrade went ok, there were no problems.)

I attached the output of "grep setroubleshoot /var/log/messages" as a text file to this bug.

I have reinstalled selinux-policy and selinux-policy-targeted and done a "autorelabel" but it doesn't help.

I compared several files with a second fc14 system which has been upgraded from fc13 and don't see differences.

I must be missing something but what?

Please help me!



Version-Release number of selected component (if applicable):

selinux-policy-3.9.7-40.fc14.noarch
selinux-policy-targeted-3.9.7-40.fc14.noarch



How reproducible: All the time.


Steps to Reproduce:
1.
2.
3.
  
Actual results: A lot of SELinux errors, see attachment.


Expected results: No selinux errors.


Additional info:

Comment 1 Eddie Lania 2011-05-07 20:33:42 UTC
*** Bug 702793 has been marked as a duplicate of this bug. ***

Comment 2 Eddie Lania 2011-05-07 20:34:33 UTC
*** Bug 702795 has been marked as a duplicate of this bug. ***

Comment 3 Eddie Lania 2011-05-07 20:35:23 UTC
*** Bug 702796 has been marked as a duplicate of this bug. ***

Comment 4 Eddie Lania 2011-05-07 20:36:47 UTC
*** Bug 702797 has been marked as a duplicate of this bug. ***

Comment 5 Eddie Lania 2011-05-07 20:37:29 UTC
*** Bug 702798 has been marked as a duplicate of this bug. ***

Comment 6 Eddie Lania 2011-05-07 20:38:17 UTC
*** Bug 702799 has been marked as a duplicate of this bug. ***

Comment 7 Eddie Lania 2011-05-07 20:38:58 UTC
*** Bug 702800 has been marked as a duplicate of this bug. ***

Comment 8 Eddie Lania 2011-05-07 20:39:47 UTC
*** Bug 702801 has been marked as a duplicate of this bug. ***

Comment 9 Eddie Lania 2011-05-07 20:40:38 UTC
*** Bug 702802 has been marked as a duplicate of this bug. ***

Comment 10 Eddie Lania 2011-05-08 08:52:33 UTC
Also, when I login via ssh i get this message:

"Unable to get valid context for root"

And when I try to (re)install selinux-policy-targeted, i get:

  Installing     : selinux-policy-targeted-3.9.7-40.fc14.noarch                                                                                          1/1 
libsepol.permission_copy_callback: Module mediawiki depends on permission read_policy in class security, not satisfied (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file or directory).
semodule:  Failed!

Installed:
  selinux-policy-targeted.noarch 0:3.9.7-40.fc14                                                                                                             

Complete!

I really hope somebody (Daniel?) is able to help me with this issue soon.

Regards,

Eddie.

Comment 11 Eddie Lania 2011-05-08 14:33:31 UTC
Hereby I add another attachment, it's the daily logwatch report from the system affected by this problem.

I think that there is more useful information in it.

Regards,

Eddie.

Comment 12 Eddie Lania 2011-05-08 14:34:42 UTC
Created attachment 497644 [details]
Logwatch of the problematic system

Comment 13 Eddie Lania 2011-05-08 19:28:49 UTC
I seem to have solved it myself by:

1. setenforce 0
2. removing selinux-policy and selinux-policy-targeted
3. reinstalling selinux-policy and selinux-policy-targeted
4. re-enabling selinux
5. touch /.autorelabel
6. reboot

Comment 14 Eddie Lania 2011-05-08 19:30:09 UTC
in comment 13, i forgot that between step 2 and 3 i removed /etc/selinux/targeted.

Comment 15 Miroslav Grepl 2011-05-09 15:42:10 UTC
Eddie,
could you try to do these steps

# setenforce 0
# rm -rf /etc/selinux/targeted
# yum reinstall selinux-policy-targeted
# fixfiles restore
# reboot

Comment 16 Eddie Lania 2011-05-09 18:53:28 UTC
Thank you Miroslav but isn't that basically the same as the steps I described in comment 13 and 14? It seems that everything is running fine now I have done that.
Do I still need to do your steps as well?

Comment 17 Miroslav Grepl 2011-05-09 19:21:11 UTC
You are right. I missed the comment #14.

The problem is I added some fixes (relating to read_policy) to RHEL6 (and it means these changes are also in F13). And these changes are not in Fedora 14.

Comment 18 Elad Alfassa 2011-05-10 19:03:07 UTC
Moving to selinux-policy (was 0xFFFF)



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 19 Miroslav Grepl 2011-05-22 18:12:38 UTC
*** Bug 706750 has been marked as a duplicate of this bug. ***

Comment 20 Miroslav Grepl 2011-05-24 06:03:07 UTC
*** Bug 707090 has been marked as a duplicate of this bug. ***

Comment 21 Miroslav Grepl 2011-05-27 08:41:31 UTC
Fixed in selinux-policy-3.9.7-42.fc14

Comment 22 Fedora Update System 2011-05-27 15:45:59 UTC
selinux-policy-3.9.7-42.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-42.fc14

Comment 23 Fedora Update System 2011-05-27 20:27:56 UTC
Package selinux-policy-3.9.7-42.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.9.7-42.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-42.fc14
then log in and leave karma (feedback).

Comment 24 Eddie Lania 2011-06-01 18:02:41 UTC
Updated:
  selinux-policy.noarch 0:3.9.7-42.fc14

Dependency Updated:
  selinux-policy-targeted.noarch 0:3.9.7-42.fc14

Looks fine to me.

However, the one system i had this issue on already was being fixed by the steps in comment #13 and #14.

Regards,

Eddie.

Comment 25 Adam Pribyl 2011-06-12 18:41:54 UTC
I had the same problem - this is still not in updates. I "fixed" it by deleting of /etc/selinux/targeted but it was not a good advice as I lost my modifications to the policy...

Comment 26 Miroslav Grepl 2011-06-13 10:45:59 UTC
Well, my fault. I would say

# mv /etc/selinux/targeted /etc/selinux/targeted.backup

instead of

# rm -rf /etc/selinux/targeted

Did you have a lot of rules in your local modules?

Comment 27 Adam Pribyl 2011-06-13 15:28:23 UTC
Acctualy it is not that bad. I have a backups. Just want to make a note for others to save some headache.

Comment 28 Fedora Update System 2011-07-12 05:15:22 UTC
selinux-policy-3.9.7-42.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.