-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
None
-
None
-
rhel-sst-network-management
-
ssg_networking
-
None
-
-
False
-
-
None
-
None
-
None
-
None
-
None
Description of problem:
DNS doesn't gets updated when NNCP policy is applied
Version-Release number of selected component (if applicable):
4.12.z
How reproducible:
Always in customer environment
Steps to Reproduce:
Customer has applied a NNCP policy to change the third IP in the `/etc/resolv.conf` . The initial configuration was of resolv.conf was
cat /etc/resolv.conf # Generated by NetworkManager nameserver x-ipv4-0000000001-x nameserver x-ipv4-0000000002-x nameserver x-ipv4-0000000004-x
Customer has tried to update the NNCP as follows:
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
name: nameserver-dns-config
spec:
nodeSelector:
node-role.kubernetes.io/worker: ""
maxUnavailable: 1
desiredState:
dns-resolver:
config:
search: []
server:
- x-ipv4-0000000001-x
- x-ipv4-0000000002-x
- x-ipv4-0000000003-x
# - x-ipv4-0000000004-x
The configuration gets applied correctly and is visible in the nmstate handler logs and the nnce is successful. However it doesn't gets updated in resolv.conf . Looking into the nmcli connection show it seems like one for the field is not getting updated. Also there is no DHCP involved in the configuration.
nmcli connection show ens192 | grep -i dns connection.mdns: -1 (default) connection.dns-over-tls: -1 (default) ipv4.dns: x-ipv4-0000000001-x,x-ipv4-0000000002-x,x-ipv4-0000000003-x ipv4.dns-search: -- ipv4.dns-options: -- ipv4.dns-priority: 40 ipv4.ignore-auto-dns: no ipv6.dns: -- ipv6.dns-search: -- ipv6.dns-options: -- ipv6.dns-priority: 0 ipv6.ignore-auto-dns: no IP4.DNS[1]: x-ipv4-0000000001-x IP4.DNS[2]: x-ipv4-0000000002-x IP4.DNS[3]: x-ipv4-0000000004-x
Expected results:
DNS should get updated in the /etc/resolv.conf file
Additional info:
