Bug 858336 - Missing directory for log
Summary: Missing directory for log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openshift-origin-broker
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-18 17:21 UTC by Michael S.
Modified: 2012-12-20 15:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-20 15:10:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael S. 2012-09-18 17:21:58 UTC
After fixing all others bugs ( see 858326, 858319, 858301 ), the last problem appeared :

All rails config ( test, production, developpement ) have the same log file :
/var/log/stickshift/user_action.log

and this directory do not exist. 

So in order to make it work fine, a directory /var/log/stickshift/ , with owner apache, should be created in the rpm. I let the selinux issue as a exercise, since I am running it as permissive for now.

Comment 1 Fedora Update System 2012-09-24 17:02:04 UTC
openshift-origin-broker-0.6.7-11.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/openshift-origin-broker-0.6.7-11.fc18

Comment 2 Fedora Update System 2012-09-24 20:02:12 UTC
Package openshift-origin-broker-0.6.7-11.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openshift-origin-broker-0.6.7-11.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-14671/openshift-origin-broker-0.6.7-11.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-12-20 15:10:55 UTC
openshift-origin-broker-0.6.7-11.fc18 has been pushed to the Fedora 18 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.