Bug 2133858
| Summary: | [RFE] Support the DNS priority | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Wen Liang <wenliang> |
| Component: | rhel-system-roles | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Jon Trossbach <jtrossba> |
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | unspecified | ||
| Version: | 9.2 | CC: | jtrossba, pasik, rhel-cs-system-management-subsystem-qe, rmeggins, spetrosi |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | role:network | ||
| Fixed In Version: | rhel-system-roles-1.21.0-0.2.network.el9 | Doc Type: | Enhancement |
| Doc Text: |
.The `network` System Role supports setting a DNS priority value
This enhancement adds the `dns_priority` parameter to the RHEL `network` System Role. You can set this parameter to a value from `-2147483648` to `2147483647`. The default value is `0`. Lower values have a higher priority. Note that negative values cause the System Role to exclude other configurations with a greater numeric priority value. Consequently, in presence of at least one negative priority value, the System Role uses only DNS servers from connection profiles with the lowest priority value.
As a result, you can use the `network` System Role to define the order of DNS servers in different connection profiles.
|
Story Points: | --- |
| Clone Of: | 2133856 | Environment: | |
| Last Closed: | 2023-05-09 07:37:56 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: | 2133856 | ||
| Bug Blocks: | |||
|
Comment 3
Jon Trossbach
2022-12-19 14:54:48 UTC
For this I will be testing ests/tests_eth_dns_support_nm.yml and tests/tests_ipv6_dns_search_nm.yml unless I hear otherwise Ansible 2.14 RHEL 6.10 fails as expected. Everything else passes. [root@netqe4 Upstream-testsuite]# rpm -q rhel-system-roles rhel-system-roles-1.21.0-0.13.el9.noarch [root@netqe4 Upstream-testsuite]# uname -r 5.14.0-230.el9.x86_64 tests_eth_dns_support_nm.yml tests_ipv6_dns_search_nm.yml :: [ 14:53:36 ] :: [ FAIL ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1) :: [ 14:53:35 ] :: [ FAIL ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 2) :: [ 15:47:48 ] :: [ FAIL ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1) :: [ 15:47:47 ] :: [ FAIL ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 2) :: [ 14:54:50 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0) :: [ 14:54:49 ] :: [ PASS ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 0) :: [ 15:49:04 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0) :: [ 15:49:03 ] :: [ PASS ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 0) :: [ 14:56:31 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0) :: [ 14:56:30 ] :: [ PASS ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 0) :: [ 15:50:48 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0) :: [ 15:50:47 ] :: [ PASS ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 0) :: [ 14:58:02 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0) :: [ 14:58:01 ] :: [ PASS ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 0) :: [ 15:52:11 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0) :: [ 15:52:10 ] :: [ PASS ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 0) :: [ 14:59:25 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0) :: [ 14:59:23 ] :: [ PASS ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 0) :: [ 15:53:27 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0) :: [ 15:53:26 ] :: [ PASS ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 0) :: [ 15:00:43 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0) :: [ 15:00:42 ] :: [ PASS ] :: Test tests_eth_dns_support_nm.yml (Assert: expected 0, got 0) :: [ 15:54:44 ] :: [ PASS ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0) :: [ 15:54:43 ] :: [ PASS ] :: Test tests_ipv6_dns_search_nm.yml (Assert: expected 0, got 0) 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/RHEA-2023:2246 |