Bug 1321533

Summary:	Logging deployer pod failed when processing logging-fluentd-template
Product:	OKD	Reporter:	Xia Zhao <xiazhao>
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED CURRENTRELEASE	QA Contact:	chunchen <chunchen>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.x	CC:	aos-bugs, ewolinet, lmeyer, wsun
Target Milestone:	---	Keywords:	Regression, TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-12 17:12:14 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:

Comment 2 Xia Zhao 2016-03-30 05:47:46 UTC

After doing oadm policy "add-cluster-role-to-user cluster-admin system:serviceaccount:logging:logging-deployer" on the master machine,logging deployer pod got completed successfully. 
Checked logging docs at https://docs.openshift.org/latest/install_config/aggregate_logging.html#pre-deployment-configuration, it is not updated. Will address the doc issue seperately, closing this issue as verified.

Comment 3 Luke Meyer 2016-03-30 14:05:51 UTC

Origin code changed so that project editor (which is the deployer role) no longer can administer daemonsets. We actually do not want to make the deployer a cluster-admin due to security concerns of the cluster-admin token being on a node briefly; that's only something we'd recommend as a temporary fix to get past this. The long-term fix will be to add some custom roles to the deployer service account. That's coming with this PR: https://github.com/openshift/origin-aggregated-logging/pull/98/commits/7f8d77aacf790b21f302d23ea9bc29920e63940a

Xia, if you have an origin issue to track this, or a docs issue, please note those here. I found some other errors in the docs that need fixing anyway, and will also queue up some doc fixes related to this change.

Comment 4 Xia Zhao 2016-03-31 03:25:44 UTC

@lmeyer Thank you so much for the info. 
I have an OSE issue which has been proved to be the same root cause: https://bugzilla.redhat.com/show_bug.cgi?id=1321855
And a doc issue correspondingly:
https://bugzilla.redhat.com/show_bug.cgi?id=1322249

BTW, I feel interested on "other errors in the docs that need fixing", hope to be updated with the material you will create here, would you please notify me in future when you are done and convenient? Thanks in advance!

Comment 5 Xia Zhao 2016-03-31 06:20:42 UTC

@lmeyer 
Please also find another suspect issue for OSE 3.2:
 Logging deployer created logging-support-template in default namespace instead of the one specified for logging
https://bugzilla.redhat.com/show_bug.cgi?id=1322245