Fixed IP bonding Openshift configuration leads to no dns resolution on node

Solution Unverified - Updated -

Issue

When configuring Fixed ip bonding in OCP 4 with following configuration described in Openshift documentation:

nomodeset
rd.neednet=1
coreos.inst=yes
coreos.inst.install_dev=sda
coreos.live.rootfs_url=http://{IGNITION_WEBSERVER_IP}/rhcos-live-rootfs.img
coreos.inst.ignition_url=http://{IGNITION_WEBSERVER_IP}/physical-worker.ign
bond=bond0:eno1,eno2:mode=802.3ad,miimon=100,updelay=1200
ip={NIC_IP}::{GW_IP}:{NETMASQ}:{HOSTNAME}:bond0:none 
nameserver={NS1_IP}
nameserver={NS2_IP}

After first reboot, the nodes cannot resolve dns names.

Environment

  • Openshift Container Platform (OCP) 4.6

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