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.
This doesn't seem specifically related to logging.
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.
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.