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

Bug 1441889

Summary:	Cannot deploy logging via "logging-deployer" image with oc cluster up
Product:	OpenShift Container Platform	Reporter:	Dongbo Yan <dyan>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Dongbo Yan <dyan>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	aos-bugs, cbucur, cewong, chernand, jokerman, mmccomas, nschuetz, rmeggins, wzheng, xiuwang
Target Milestone:	---
Target Release:	3.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-11 10:47:38 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:
Bug Depends On:
Bug Blocks:	1444221

Comment 1 Dongbo Yan 2017-04-13 02:19:41 UTC

Since brew image have already pushed into registry.access.redhat.com, you can reproduce like:
$ oc cluster up --image=registry.access.redhat.com/openshift3/ose --version=v3.5 --logging

no need other extra steps

Comment 2 Jeff Cantrill 2017-05-01 18:35:09 UTC

*** Bug 1444221 has been marked as a duplicate of this bug. ***

Comment 3 Jeff Cantrill 2017-05-11 15:38:04 UTC

Workaround is to use oc cluster up  without the logging switch and then openshift-ansible to deploy logging.

Comment 8 Dongbo Yan 2017-06-23 03:09:05 UTC

Test with 
brew-pulp.../openshift3/logging-deployer        v3.5.5.28           474e04efb614        36 hours ago        885.2 MB

could deploy logging with oc cluster up

change to verified

Comment 10 Codrin Bucur 2017-07-10 22:22:18 UTC

@Jeff Cantril

Regarding the workaround, can you please detail the steps for running openshift-ansible to deploy logging, when using oc cluster up?

Thanks!
-Codrin

Comment 11 errata-xmlrpc 2017-07-11 10:47:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1640