Bug 882356 - The problem of access to the data after an upgrade system
Summary: The problem of access to the data after an upgrade system
Keywords:
Status: CLOSED DUPLICATE of bug 882255
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-30 18:30 UTC by Fomalhaut
Modified: 2012-12-03 08:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-03 08:08:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fomalhaut 2012-11-30 18:30:59 UTC
The problem of access to the data after an upgrade system

Description of problem: after an upgrade (http://paste.stg.fedoraproject.org/2119/) immediately began to appear error SELinux (http://paste.stg.fedoraproject.org/2120/) and lost access to the files on the mounted two disks (http://paste.stg.fedoraproject.org/2121/). Did "touch /. Autorelabel; reboot", but it did not help. Checked S.M.A.R.T. - HDD was in order. On one of the drives to check the file system: http://paste.stg.fedoraproject.org/2122/. Then do "setenforce 0" - data immediately become available. The errors SELinux and continue to appear in SETroubleshoot.

Version-Release number of selected component (if applicable): Before the update: 3.11.1-50.fc18.noarch (@koji-override-0/$releasever), after the update: 3.11.1-57.fc18.noarch (@updates-testing).

How reproducible: Set SELinux update to 3.11.1-57.fc18.noarch

Actual results: Enabling SELinux denies access to files, disabling SELinux immediately solve the problem. The files on system partitions (new Fedora 18 and previous Fedora 16) are available in every state of SELinux.

Expected results: correct work of SELinux

Additional info: dmesg - http://paste.stg.fedoraproject.org/2118/ ; /var/log/messages - http://paste.stg.fedoraproject.org/2123/

P.S. I used "Google Translate" to translate russian -> english

Comment 1 Miroslav Grepl 2012-12-03 08:08:22 UTC

*** This bug has been marked as a duplicate of bug 882255 ***


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