Bug 1033274 - Wrong SELinux context for several files in F20 TC2 AMIs
Summary: Wrong SELinux context for several files in F20 TC2 AMIs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: appliance-tools
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-21 19:49 UTC by Vitaly Kuznetsov
Modified: 2015-06-29 13:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:06:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vitaly Kuznetsov 2013-11-21 19:49:39 UTC
Description of problem:
I'm testing F20-TC2 AWS AMIs (ami-3392b55a, ami-f794b39e) in EC2.

# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ /
restorecon reset /var/cache/yum context system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0
restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0
restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0


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


How reproducible:
always

Steps to Reproduce:
1. Run EC2 instance F20-TC2 AMI
2. Try restoring contexts with restorecon

Actual results:
/var/cache/yum, /var/log/boot.log, /boot/extlinux/ldlinux.sys contexts are wrong

Expected results:
all contexts are ok

Additional info:
dwalsh: "These should be opened as a bug in anaconda. (The file_t ones anyways.)"

Comment 1 Matthew Miller 2013-11-21 20:34:19 UTC
We're building these images with appliance-creator, so it's not anaconda's fault.

Comment 2 Fedora Admin XMLRPC Client 2014-01-12 19:52:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-05-29 09:49:31 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 13:06:10 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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