Bug 598936 - Error on installing - tried fixfiles relabel still broken
Summary: Error on installing - tried fixfiles relabel still broken
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted   
(Show other bugs)
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 11:22 UTC by David
Modified: 2010-10-09 23:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-09 23:22:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description David 2010-06-02 11:22:15 UTC
Description of problem:

Running Transaction
  Installing     : selinux-policy-3.7.19-22.fc13.noarch                     1/2 
  Installing     : selinux-policy-targeted-3.7.19-22.fc13.noarch            2/2 
libsepol.context_from_record: type httpd_sys_rw_content_rw_t is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert system_u:object_r:httpd_sys_rw_content_rw_t:s0 to sid
invalid context system_u:object_r:httpd_sys_rw_content_rw_t:s0
libsemanage.semanage_install_active: setfiles returned error code 1.
semodule:  Failed!

Installed:
  selinux-policy.noarch 0:3.7.19-22.fc13                                        
  selinux-policy-targeted.noarch 0:3.7.19-22.fc13

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2010-06-02 12:21:14 UTC
Fixed in selinux-policy-3.7.19-23.fc13

Should be in updates-testing or koji


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