What were you trying to do that didn't work?

Given system configured with DHCP for gateway interface,
When user apply desired state with static DNS search domains only,
Then nmstate is not using NetworkManager global DNS to store the desired static DNS search domain.

What is the impact of this issue to you?

When using OpenShift on AWS or other cloud services where DHCP server is not configured by OpenShift user, user will lose this static DNS search domains upon node reboot.

Please provide the package NVR for which the bug is seen:

nmstate-2.2.48-1.el9

How reproducible is this bug?:

100%

Steps to reproduce

echo '---
dns-resolver:
  config: {}
interfaces:
  - name: eth1
    type: ethernet
    state: up
    ipv4:
      dhcp: true
      enabled: true
    ipv6:
      enabled: false' | sudo nmstatectl apply -

echo '
---
dns-resolver:
  config:
    search:
      - example.com
      - example.org' | sudo nmstatectl apply -

Expected results

/var/lib/NetworkManager/NetworkManager-intern.conf contains the static search domain, but DHCP provides DNS nameserver still applied to /etc/resolv.conf

Actual results

/var/lib/NetworkManager/NetworkManager-intern.conf does not contain static search domain.