Hide Forgot
Description of problem: nmcli connection modify +ipv4.dns-options does not append options Version-Release number of selected component (if applicable): RHEL8 beta NetworkManager-1.14.0-5.el8.x86_64 How reproducible: RHEL8 beta or RHEL7 any release, notice how dns-options does not behave the same as dns-search though both are array of string according to nm-settings manpage. Steps to Reproduce: 1. # nmcli con mod "System ens3" ipv4.dns-search "abc.com" # nmcli con mod "System ens3" ipv4.dns-options "ndots:2" 2. # nmcli con show "System ens3" | grep -e ipv4.dns-search -e ipv4.dns-options ipv4.dns-search: abc.com ipv4.dns-options: "ndots:2" 3. # nmcli con mod "System ens3" +ipv4.dns-search "redhat.com" # nmcli con mod "System ens3" +ipv4.dns-options "timeout:2" Actual results: dns-options contains only timeout:2 # nmcli con show "System ens3" | grep -e ipv4.dns-search -e ipv4.dns-options ipv4.dns-search: abc.com,redhat.com ipv4.dns-options: "timeout:2" Expected results: dns-options should contain both ndots:2 and timeout:2 # nmcli con show "System ens3" | grep -e ipv4.dns-search -e ipv4.dns-options ipv4.dns-search: abc.com,redhat.com ipv4.dns-options: "ndots:2 timeout:2" Additional info: dns-options should behave the same as dns-search since: # man nm-settings 2>/dev/null | grep -e dns-options -e dns-search │dns-options │ array of string │ [] │ Array of DNS options as │ │dns-search │ array of string │ [] │ Array of DNS search │
Fixed upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/9b0c1ef5d001ad0b2b9173e104871c91f4c95426 Note that it's also possible to specify multiple options in the same command: nmcli connection modify "System ens3" ipv4.dns-options debug,rotate,ndots:5
Taking out of the 8.2 RPL.. Fix already in 8.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3623