Bug 1960111

Summary: Port 8080 of oVirt CSI driver is causing collisions with other services
Product: OpenShift Container Platform Reporter: nijin ashok <nashok>
Component: StorageAssignee: Benny Zlotnik <bzlotnik>
Storage sub component: oVirt CSI Driver QA Contact: Guilherme Santos <gdeolive>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, bzlotnik, gchakkar, gzaidman, mburman, mueller, wduan
Version: 4.6Flags: bzlotnik: needinfo-
Target Milestone: ---   
Target Release: 4.7.z   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-15 09:27:49 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:
Bug Depends On:    
Bug Blocks: 1960149    

Description nijin ashok 2021-05-13 04:54:32 UTC
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:

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:

Comment 3 Thomas Mueller 2021-05-19 05:50:19 UTC
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

Comment 9 Guilherme Santos 2021-05-31 18:36:07 UTC
Verified on:

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

pods running as expected and no "CrashLoopBackOff"

Comment 11 Siddharth Sharma 2021-06-04 18:39:36 UTC
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

Comment 15 errata-xmlrpc 2021-06-15 09:27:49 UTC
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.