-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.17.0
-
None
-
Important
-
None
-
False
-
Description of problem:
cannot create dns recover NNCP which use clear dns configuration in node.
Version-Release number of selected component (if applicable):
4.17.0-0.nightly-2024-12-31-045652
How reproducible:
always
Steps to Reproduce:
1.create dns NNCP in one node apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: staticdns-test spec: nodeSelector: kubernetes.io/hostname: worker-00.yinzhou69063.qe.devcluster.openshift.com desiredState: dns-resolver: config: search: - example.com server: - 147.75.207.207 - 2003::3 // check dns configuration in node sh-5.1# cat /etc/resolv.conf # Generated by NetworkManager search example.com yinzhou69063.qe.devcluster.openshift.com nameserver 147.75.207.207 nameserver 2003::3 2. create dns recover nncp to clear this configuration kind: NodeNetworkConfigurationPolicy apiVersion: nmstate.io/v1 metadata: name: dns-1 namespace: openshift-nmstate spec: nodeSelector: kubernetes.io/hostname: worker-00.yinzhou69063.qe.devcluster.openshift.com desiredState: dns-resolver: config: search: server: 3. NNCP create failed $ oc get nncp NAME STATUS REASON dns-1 Degraded FailedToConfigure
Actual results:
NNCP create failed
Expected results:
NNCP create successfully
Additional info: