Description of problem: knmstate listens on port 8080 on cluster nodes. The port is meant for metrics, but we never use it. It just happens to be enabled by default. Due to this, we collide with another cluster component Bug 1896320. Version-Release number of selected component (if applicable): CNV 2.4, 2.5 OCP 4.6 ovirt provider How reproducible: Always Steps to Reproduce: 1. Deploy CNV on OCP on oVirt Actual results: https://bugzilla.redhat.com/show_bug.cgi?id=1896320 Expected results: Smooth upgrade. Additional info:
Can we somehow let k8s allocate a free nodePort instead of hard-coding 8080?
Verified on: $ oc version Client Version: 4.6.0-202010271321.p0-ffd6836 Server Version: 4.6.7 Kubernetes Version: v1.19.0+1348ff8 $ oc get csv -n openshift-cnv NAME DISPLAY VERSION REPLACES PHASE kubevirt-hyperconverged-operator.v2.5.2 OpenShift Virtualization 2.5.2 kubevirt-hyperconverged-operator.v2.5.1 Succeeded registry.redhat.io/container-native-virtualization/kubernetes-nmstate-handler-rhel8@sha256:b323cf93cac96d4a4a840b84232be4a1fa90121506c8f28e5336a49f4b78030f 1. Shell to one of the nmstate-handler pods in the cluster: $ oc exec -n openshift-cnv -it nmstate-handler-4x4nl -- bash 2. Verify no one is listening on port 8080: [root@test-252-lg4gx-worker-0-5w9v5 /]# ss -ap | grep -w 8080 [root@test-252-lg4gx-worker-0-5w9v5 /]#
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 (OpenShift Virtualization 2.5.2 Images), 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/RHEA-2020:5560
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days