Description of problem: The request is mainly to backport the upstream fix https://github.com/openshift/ovirt-csi-driver/pull/53. In one of the customer environment, the ovirt-csi-driver-node was in "CrashLoopBackOff" status since port 8080 was used by another service. The user had to delete the conflicting service to make the pod up. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create another service to listen on port 8080. Actual results: Port 8080 of oVirt CSI driver is causing collisions with other services Expected results: Backport https://github.com/openshift/ovirt-csi-driver/pull/53 Additional info:
IMHO the issue depends on the external ip. The ovirt container fails to bind to 8080 only on the node which has added the additional IP to the interface. My take on formulating "Steps to Reproduce": 1. Create a service with external IP to listen on port 8080. 2. ensure the services external ip is added to some nodes primary network interface
Verified on: 4.7.0-0.nightly-2021-05-28-053625 Steps: 1. created nginx service on port 8080 # oc new-app nginx:1.16~https://github.com/sclorg/nginx-container.git --context-dir=1.16/test/test-app/ 2. checked ovirt-csi-driver-node pods # oc get pods -n openshift-cluster-csi-drivers Results: pods running as expected and no "CrashLoopBackOff"
This bug will be shipped as part of next z-stream release 4.7.15 on June 14th, as 4.7.14 was dropped due to a regression https://bugzilla.redhat.com/show_bug.cgi?id=1967614
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 (Moderate: OpenShift Container Platform 4.7.16 security and bug fix update), 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/RHSA-2021:2286