Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 880385

Summary: MCollective client log file ownership problem
Product: OpenShift Container Platform Reporter: Brenton Leanhardt <bleanhar>
Component: DocumentationAssignee: Bilhar <baulakh>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 1.2.0CC: erich, jeder, jokerman, libra-onpremise-devel, lmeyer, mmasters, mmccomas
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-05 18:19:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brenton Leanhardt 2012-11-26 21:04:50 UTC 
Description of problem:
This is related to Bug #849558.  We need the deployment guide updated to state that users must fix the file ownership in order for the Broker's Apache instance to be able to write to /var/log/mcollective-client.log.


chown root:apache /var/log/mcollective-client.log
Comment 2 Brenton Leanhardt 2012-12-04 13:09:47 UTC 
Correction, this should be:

chown apache:root /var/log/mcollective-client.log
Comment 3 Bilhar 2013-01-10 10:55:04 UTC 
I'm not quite sure what exactly to update in the Deployment Guide. Can you please point me to the section that is impacted by this?
Comment 4 Brenton Leanhardt 2013-01-10 13:23:21 UTC 
In Section 5.6 we need to add that command somewhere.  Without it the broker will not be able to log to that file.  This is not something we can do in the broker RPM because that file is not owned by any package.  

It would make sense to have the command run right after the "Configuring the MCollective Client" section because that is where we first mention /var/log/mcollective-client.log
Comment 5 Bilhar 2013-01-15 01:06:44 UTC 
This will be fixed in the next release.
Comment 8 Luke Meyer 2013-02-05 18:19:58 UTC 
These are released AFAIK, apparently not in the errata release.