Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1918658

Summary:	No dns configuration after first reboot with bonding and fixed ip
Product:	OpenShift Container Platform	Reporter:	Simon Belmas-Gauderic <sbelmasg>
Component:	RHCOS	Assignee:	Luca BRUNO <lucab>
Status:	CLOSED DUPLICATE	QA Contact:	Michael Nguyen <mnguyen>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6.z	CC:	bbreard, dustymabe, imcleod, jligon, miabbott, nstielau
Target Milestone:	---
Target Release:	4.8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-29 14:09:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Simon Belmas-Gauderic 2021-01-21 10:28:00 UTC

Version:

Openshift 4.6.9

Platform:

Baremetal

* UPI (semi-manual installation on customized infrastructure)

What happened?
When using bonded interfaces with static ip, at first reboot, Dns are not configured on CoreOS

What did you expect to happen?

Dns is configured after first reboot.

How to reproduce it (as minimally and precisely as possible)?

Comment 3 Dusty Mabe 2021-01-21 16:36:22 UTC

Hey Simon,

There are some issues with `nameserver=` kernel argument handling in NetworkManager in RHCOS/OCP 4.6. See https://bugzilla.redhat.com/show_bug.cgi?id=1882781 for more details.

Can you share the contents of the files in `/etc/NetworkManager/system-connections/` ? The output of a command like `sudo tail -n 100 /etc/NetworkManager/system-connections/*` should do.

Comment 8 Luca BRUNO 2021-01-29 14:09:33 UTC

Reading through the BZ and the support case, it looks like the customer initially hit https://bugzilla.redhat.com/show_bug.cgi?id=1882781 on 4.6 (nameserver= bug).
They then proceeded with a workaround through `ip=` and they managed to get it working.
The same customer seems to have other support cases in flights (on "bonding and ovn"), which got partially mixed in here.

Thus I'm closing this BZ as a duplicate of the one above, concerning the nameserver= bug only. Other networking issues, if any, can be tracked in their own BZ.

*** This bug has been marked as a duplicate of bug 1882781 ***