Description of problem: It has been observed that when applying NNCP that defines only global DNS config and does not configure any interface specifically, the gateway interface is converted from unmanaged to managed. This is not desired for various reasons, but to simplify it can be said that global DNS config should not be creating any specific per-interface configuration. Version-Release number of selected component (if applicable): nmstate-1.0.2-21.el8_4 How reproducible: Always Steps to Reproduce: 1. Create NNCP with `.spec.desiredState.dns-resolver.config.search` and `.spec.desiredState.dns-resolver.config.server` 2. Make sure NNCP doesn't define any per-interface config Actual results: Gateway interface gets converted from unmanaged to managed with DNS configuration from NNCP applied to it Expected results: Configuration of gateway interface is not changed. DNS is applied globally
Please note this affects a customer with OCP 4.10, thus it needs a backport back to 8.4
Summery on the fix. With nmstate-1.4.3-1.el8, nmstate will not store DNS configurations to interface which is unmanaged or external managed in NetworkManager, but using global DNS directly.
Created attachment 1963166 [details] verified.log Verified with: nmstate-1.4.4-2.el8.x86_64 nispor-1.2.10-1.el8.x86_64 NetworkManager-1.40.16-4.el8.x86_64 DISTRO=RHEL-8.9.0-20230503.20