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

Bug 2098574

Summary:	The dns nncp applied not to all nodes
Product:	OpenShift Container Platform	Reporter:	Aleksandra Malykhin <amalykhi>
Component:	Networking	Assignee:	Ben Nemec <bnemec>
Networking sub component:	kubernetes-nmstate-operator	QA Contact:	Aleksandra Malykhin <amalykhi>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	medium	CC:	bgalvani, davegord, fge
Version:	4.10
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2134563 (view as bug list)		Environment:
Last Closed:	2023-01-16 16:58:43 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:
Bug Depends On:	2134563, 2135734
Bug Blocks:

Description Aleksandra Malykhin 2022-06-20 06:17:54 UTC

Description of problem:

Verified on the BM IPI deployment.
The dns resolver is not update on 2/5 nodes.

Version-Release number of selected component (if applicable):
Cluster version is 4.10.18

Kubernetes NMState Operator   4.10.0-202205311508  (latest)
How reproducible:
100%

Steps to Reproduce:
1. Deploy the cluster
2. Apply the nncp https://github.com/nmstate/kubernetes-nmstate/blob/main/docs/examples/dns.yaml
3. Wait that it is applied
oc get nnce -w
4. Verify the new configuration
$ cat /etc/resolv.conf on every nodes

Actual results:
The dns resolver updated on the 3 nodes of 5
All nnce are "Available"

Expected results:

All the nodes are updated.

Additional info:

Comment 9 Beniamino Galvani 2022-10-13 15:18:52 UTC

Can I reassign this to NetworkManager, or should I clone it?