Whenever mcollective-client.log is created, whether initially or due to log file rolling, it is created with the ownership of the current user.
When a root user invokes mcollective (either directly or via broker tools), there is a chance mcollective-client.log will be owned by root, preventing the broker (apache user) from writing to the log file and causing it to log errors in the httpd error_log.
The openshift.sh/ks install script now configures the mco client to log to the console at log level warn. Deploy guide should be updated to do the same.
mco client calls on the broker now log to the console instead of directly to the client log file. When used from the broker application, this means warnings and errors will be directed to the application error log in /var/log/openshift/broker/httpd/error_log. When used via broker scripts (e.g. oo-admin-ctl-district) these would actually print out on the console. At log_level warn, though, this should only happen when there is a problem contacting the message server. If admins lower the log level to info or debug, they can expect these scripts to have some fairly verbose and confusing output, so this is discouraged.