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

Bug 1638757

Summary:	openshift-logging/config playbook fails due to missing kubeconfig
Product:	OpenShift Container Platform	Reporter:	Jatan Malde <jmalde>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED DUPLICATE	QA Contact:	Johnny Liu <jialiu>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, jokerman, mmccomas, sdodson
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-31 20:07:20 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 Jatan Malde 2018-10-12 11:55:37 UTC

Description of problem:

When running the /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/config.yml playbook, it fails when trying to determine the es version.

The reason is that the "oc command" is run without a kubeconfig.


https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/openshift_logging_elasticsearch/tasks/get_es_version.yml

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

$ oc version
oc v3.9.43
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

How reproducible:

Steps to Reproduce:
1.Configure a 3.9 OCP cluster
2. Run config.yml for openshift-logging installation on OCP
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated


Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Scott Dodson 2018-10-31 20:07:20 UTC

https://github.com/openshift/openshift-ansible/pull/10303 addressed this for 3.9

*** This bug has been marked as a duplicate of bug 1631353 ***