OpenShift 4.5 IPI on vSphere fails: Master nodes not coming up due to failing nodeip-configuration.service when using a Proxy

Solution In Progress - Updated -

Issue

  • Master Node do not complete bootstrap due to failing nodeip-configuration.servivce:
● nodeip-configuration.service - Writes IP address configuration so that kubelet and crio services select a valid node IP
   Loaded: loaded (/etc/systemd/system/nodeip-configuration.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-08-11 21:21:45 UTC; 26min ago
  Process: 1529 ExecStart=/usr/bin/podman run --rm --authfile /var/lib/kubelet/config.json --net=host --volume /etc/systemd/system:/etc/systemd/system:z registry.svc.ci.openshift.org/origin/4.5-2020-08-11-162223@sha256:54ea8cd9dba05afa87faebf283fea8dd64c7678b82840b8b7037cc9bda0acdfd node-ip set --retry-on-failure 10.3.77.2 (code=exited, status=125)
 Main PID: 1529 (code=exited, status=125)
      CPU: 77ms

Aug 11 21:21:44 lab-master-2 systemd[1]: Starting Writes IP address configuration so that kubelet and crio services select a valid node IP...
Aug 11 21:21:44 lab-master-2 podman[1529]: Trying to pull registry.svc.ci.openshift.org/origin/4.5-2020-08-11-162223@sha256:54ea8cd9dba05afa87faebf283fea8dd64c7678b82840b8b7037cc9bda0acdfd...
Aug 11 21:21:45 lab-master-2 podman[1529]:   Get https://registry.svc.ci.openshift.org/v2/: dial tcp: lookup registry.svc.ci.openshift.org on 10.2.99.196:53: no such host
Aug 11 21:21:45 lab-master-2 podman[1529]: Error: unable to pull registry.svc.ci.openshift.org/origin/4.5-2020-08-11-162223@sha256:54ea8cd9dba05afa87faebf283fea8dd64c7678b82840b8b7037cc9bda0acdfd: unable to pull image: Error initializing source docker://registry.svc.ci.openshift.org/origin/4.5-2020-08-11-162223@sha256:54ea8cd9dba05afa87faebf283fea8dd64c7678b82840b8b7037cc9bda0acdfd: error pinging docker registry registry.svc.ci.openshift.org: Get https://registry.svc.ci.openshift.org/v2/: dial tcp: lookup registry.svc.ci.openshift.org on 10.2.99.196:53: no such host
Aug 11 21:21:45 lab-master-2 systemd[1]: nodeip-configuration.service: Main process exited, code=exited, status=125/n/a
Aug 11 21:21:45 lab-master-2 systemd[1]: nodeip-configuration.service: Failed with result 'exit-code'.
Aug 11 21:21:45 lab-master-2 systemd[1]: Failed to start Writes IP address configuration so that kubelet and crio services select a valid node IP.
Aug 11 21:21:45 lab-master-2 systemd[1]: nodeip-configuration.service: Consumed 77ms CPU time

Environment

  • Red Hat OpenShift Container Platform
    • 4.5
  • VMWare vSphere
  • Installer Provisioned Infrastructure (IPI)
  • Proxy

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