cluster-network-operator failing to start metrics server on port 8080 in OpenShift Container Platform 4.16

Solution Verified - Updated -

Issue

  • During the update to OpenShift 4.16, it was observed that cluster-network-operator is stuck in CrashLoopBackOff state because of the below error reported.

    2024-09-19T16:32:46.503056041Z I0917 16:32:46.503016       1 controller.go:242] "All workers finished" controller="pod-watcher"
    2024-09-19T16:32:46.503056041Z I0917 16:32:46.503045       1 internal.go:526] "Stopping and waiting for caches"
    2024-09-19T16:32:46.503209536Z I0917 16:32:46.503189       1 internal.go:530] "Stopping and waiting for webhooks"
    2024-09-19T16:32:46.503209536Z I0917 16:32:46.503206       1 internal.go:533] "Stopping and waiting for HTTP servers"
    2024-09-19T16:32:46.503217413Z I0917 16:32:46.503212       1 internal.go:537] "Wait completed, proceeding to shutdown the manager"
    2024-09-19T16:32:46.503231142Z F0917 16:32:46.503221       1 operator.go:130] Failed to start controller-runtime manager: failed to start metrics server: failed to create listener: listen tcp :8080: bind: address already in use
    
  • It was observed that the update to OpenShift 4.16 is stuck because CNO is failing to start because of port conflict with port 8080

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.16

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content