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

Bug 892879

Summary:	Should specifying in BYO doc about adding "/var/log/mcollective-client.log" file before changing owner
Product:	OpenShift Container Platform	Reporter:	xjia <xjia>
Component:	Documentation	Assignee:	bmoss
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.0.0	CC:	adellape, bmoss, jialiu, jokerman, lcarlon, libra-onpremise-devel, lmeyer, mmccomas, xtian
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-03-20 02:37:42 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 xjia 2013-01-08 06:21:40 UTC

Description of problem:
User setup broker following the site:https://openshift.redhat.com/community/wiki/build-your-own .By default, "/var/log/mcollective-client.log" doesn't exist until execute "mco ping" on broker.  So before change the permission of mcollective-client.log, user should touch this file by themselves. This step should be written in BYO.

Version-Release number of selected component (if applicable):
https://openshift.redhat.com/community/wiki/build-your-own

How reproducible:
always

Steps to Reproduce:

Actual results:

Expected results:

Comment 3 Alex Dellapenta 2013-02-08 16:25:33 UTC

I recently went through these steps as well (sec 5.6 of the Deployment Guide) and remembered this BZ, so I made sure to touch the file first before attempting to set ownership. However, even with the file created, you get an error because the apache user doesn't exist until section 5.7.1 when the broker packages are installed, pulling in httpd. I guess you could create the user yourself at that point, but it was easier to just move on to 5.7.1 then go back and chown.

Comment 4 Luke Meyer 2013-02-08 16:54:06 UTC

(In reply to comment #3)

Good point. Actually, this is probably why even with the latest install script performing this step, the problem persists; the apache user doesn't exist when it's running.

We need to either move the command later, or yum install httpd earlier.

Comment 5 bmoss 2013-02-12 00:15:47 UTC

Luke, would the following change to the end of section 5.6.2 be sufficient to address this bug?

-----
You must also fix file ownership so that the broker host's Apache instance can write to the /var/log/mcollective-client.log file. Use the following commands to install the Apache server, create mcollective-client.log, and change the file ownership:

# yum install httpd
# touch /var/log/mcollective-client.log
# chown apache:root /var/log/mcollective-client.log

Comment 6 Luke Meyer 2013-03-13 20:59:24 UTC

Brian, I finally decided that it made less sense to install httpd here than to just do the file fixup later.

Thus, please add a section after 5.7.2. Modifying Broker Proxy Configuration, to the effect of what you have in #5 (minus the Apache install). It seems a little out of place but it is enabling the broker app to log correctly, so I consider it broker conf.