Bug 2041627

Summary: Set DNS search setting only for enabled IP protocols
Product: Red Hat Enterprise Linux 8 Reporter: Rich Megginson <rmeggins>
Component: rhel-system-rolesAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: David Jež <djez>
Severity: unspecified Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: unspecified    
Version: 8.6CC: djez, ferferna, fge, gfialova, nhosoi, rmeggins, spetrosi, till, wenliang, zhguan
Target Milestone: rcKeywords: Triaged
Target Release: 8.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:network
Fixed In Version: rhel-system-roles-1.13.0-1.el8 Doc Type: Bug Fix
Doc Text:
.The Networking System Role no longer fails to set a DNS search domain if IPv6 is disabled Previously, the `nm_connection_verify()` function of the `libnm` library did not ignore the DNS search domain if the IPv6 protocol was disabled. As a consequence, when you used the Networking RHEL System Role and set `dns_search` together with `ipv6_disabled: true`, the System Role failed with the following error: ---- nm-connection-error-quark: ipv6.dns-search: this property is not allowed for 'method=ignore' (7) ---- With this update, the `nm_connection_verify()` function ignores the DNS search domain if IPv6 is disabled. As a consequence, you can use `dns_search` as expected, even if IPv6 is disabled.
Story Points: ---
Clone Of: 2004899 Environment:
Last Closed: 2022-05-10 14:12:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2004899    
Bug Blocks:    

Comment 5 Zhiqian Guan 2022-01-21 06:44:56 UTC
postpone to ITM24 as ITM23 will be China public holiday

Comment 15 Zhiqian Guan 2022-02-10 08:12:27 UTC
:: [ 02:59:56 ] :: [   PASS   ] :: Test network/tests_ipv6_dns_search_nm.yml (roles/rhel-system-roles.network/tests/tests_ipv6_dns_search_nm.yml) with ANSIBLE-2.9 against RHEL_6_10_GA (Expected 0, got 0)
:: [ 03:03:06 ] :: [   PASS   ] :: Test network/tests_ipv6_dns_search_nm.yml (roles/rhel-system-roles.network/tests/tests_ipv6_dns_search_nm.yml) with ANSIBLE-2.9 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 03:05:54 ] :: [   PASS   ] :: Test network/tests_ipv6_dns_search_nm.yml (roles/rhel-system-roles.network/tests/tests_ipv6_dns_search_nm.yml) with ANSIBLE-2.9 against RHEL_8_5_0_GA (Expected 0, got 0)
:: [ 03:08:44 ] :: [   PASS   ] :: Test network/tests_ipv6_dns_search_nm.yml (roles/rhel-system-roles.network/tests/tests_ipv6_dns_search_nm.yml) with ANSIBLE-2.9 against RHEL_8_6_TESTING (Expected 0, got 0)
:: [ 03:11:15 ] :: [   PASS   ] :: Test network/tests_ipv6_dns_search_nm.yml (roles/rhel-system-roles.network/tests/tests_ipv6_dns_search_nm.yml) with ANSIBLE-2.9 against RHEL_9_TESTING (Expected 0, got 0)

[root@netqe18 Upstream-testsuite]# rpm -q rhel-system-roles
rhel-system-roles-1.13.0-1.el8.noarch

Results looks good, set this to VERIFIED

Comment 17 errata-xmlrpc 2022-05-10 14:12:50 UTC
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 (rhel-system-roles bug fix and enhancement update), 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-2022:1896