Bug 1006497 - Swift denied access to /srv/node
Summary: Swift denied access to /srv/node
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-swift
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 17:55 UTC by Adam Young
Modified: 2015-02-17 17:08 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:08:20 UTC
Type: Bug


Attachments (Terms of Use)

Description Adam Young 2013-09-10 17:55:35 UTC
Description of problem:
Swift installed from Packstack denied access to /srv/node

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


How reproducible:


Steps to Reproduce:
1.packastack --allineone
2.
3.

Actual results:
Failure during swift stage

Expected results:


Additional info:

running 
sudo audit2allow -i /var/log/audit/audit.log 

shows 
allow swift_t file_t:dir { write getattr read remove_name create open add_name };
allow swift_t file_t:file { rename write getattr read lock create open };


This can be fixed by running 
sudo restorecon -Rv /srv/node/


and rerunning packstack

Comment 1 Lon Hohberger 2013-09-10 18:04:38 UTC
The problem is a creation time vs. installation time thing - perhaps the simplest way to get this working is for the swift RPM to create /srv/node (assuming it doesn't exist) and calling restorecon on it at the time it is installed?

Comment 2 Fedora Admin XMLRPC Client 2014-08-06 15:08:02 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2014-08-06 15:43:33 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2015-01-09 19:47:36 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 5 Fedora End Of Life 2015-02-17 17:08:20 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.