vsphere-cloud-controller-manager pods in CrashLoopBackOff in RHOCP4

Solution Verified - Updated -

Issue

  • The DaemonSet of vsphere-cloud-controller takes precedence and its pods are started and running on all master nodes. When the deployment of the operator tries to deploy its pods, it runs into an issue as the port 10258 is already bound on the master nodes.

  • Getting error logs:

    failed to create listener: failed to listen on 127.0.0.1:10258: listen tcp 127.0.0.1:10258: bind: address 
already in use”.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4

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