Bug 1397210

Summary:	[RFE] if openshift_hosted_logging_deploy is set, installer should check if it is already deployed
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED NEXTRELEASE	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	aos-bugs, erjones, jokerman, mmccomas, pweil
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-13 19:37:48 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:

Description Eric Jones 2016-11-21 22:54:20 UTC

- What is the nature and description of the request? 
As an admin I require the ability to run the installer again if I need to (maintenance or other reasons) and not have to comment out `openshift_hosted_logging_deploy`.

- Why does the customer need this? (List the business requirements here) 
Becuase currently if you install the cluster with that variable set, logging deploys, but if you run the installer again without commenting that out, it tries and fails to deploy logging again.

- How would the customer like to achieve this? (List the functional requirements here) 
Check to see if logging has been deployed

- Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unable to find anything

Comment 3 Jeff Cantrill 2017-02-09 19:28:53 UTC

The 3.5 openshift_logging role is written with an attempt to be indempotent. There are places which we may have missed but the goal is to adhere to ansible principles.  In 3.4, which uses the deployer, there is no notion of being able to run over and over like with ansible.

Does this address your concern or is there more work to be done?