Bug 1572977

Summary:	[RFE] If libvirt packages are installed on metrics store machine
Product:	OpenShift Container Platform	Reporter:	Shirly Radco <sradco>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.0	CC:	aos-bugs, bugs, jokerman, lsvaty, mmccomas, rmeggins, scuppett, sradco
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1562103	Environment:
Last Closed:	2018-08-23 12:22:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1562103

Description Shirly Radco 2018-04-29 11:54:27 UTC

Description of problem:

If libvirt packages are installed on the OpenShift machine, user will run into all sorts of problems related to name resolution and DNS.

For example, the pods will not start, will be in the Error state, and will have messages like this: tcp: lookup kubernetes.default.svc.cluster.local: no such host"

Version-Release number of selected component (if applicable):
3.6

How reproducible:


Steps to Reproduce:
1. Install libvirt on the metrics store machine
2. Install OpenShift logging

Actual results:
DNS issues

Expected results:
Either check if libvirt packages are installed and abort the installation and alert the user or fix the problem that causes the issues with libvirt.

Comment 1 Jeff Cantrill 2018-04-30 01:49:01 UTC

This doesn't seem specifically related to logging.

Comment 2 Rich Megginson 2018-04-30 03:03:16 UTC

This is not logging specific.  You will run into the same problems if you try to install OpenShift on a machine where dnsmasq configured as in libvirt is running.  Maybe the installer can check to see if dnsmasq is running in a configuration that will conflict with OpenShift.

Comment 3 Stephen Cuppett 2018-08-23 12:22:02 UTC

At this point, new installs should be using leveraging a more recent release. If this issue needs addressed or is still present and recreated on a more recent release, please reopen with those details.