Hide Forgot
Description of problem: The parser for the iproute2 routing table database (/etc/iproute2/rt_tables etc.) in module_utils/network_lsr/argument_validator.py:IPRouteUtils is too strict. It asserts that entries/lines in the file are of the form `254 main` where the numeric id and the name must be separated by a single space character only. However, according to the what iproute2 does, any whitespace sequence in between the table id and table name should be considered as valid and should be accepted by the route table parser.
What playbooks need to be tested for this bug? And have they already been run in the CI system? If so where are the results?
(In reply to Jon Trossbach from comment #4) > What playbooks need to be tested for this bug? And have they already been > run in the CI system? If so where are the results? Good questions for Thomas from whom I requested the info in https://bugzilla.redhat.com/show_bug.cgi?id=2115886
Test was added in PR - https://github.com/linux-system-roles/network/pull/508/files#diff-b06f1e1bf991f123e64cf9dde6dcf9574bb279a720609a570e8af27cc2d9a359 Test coverage is in tests_unit.yml
[root@netqe2 Upstream-testsuite]# uname -r 4.18.0-416.el8.x86_64 ansible-2.9.27-1 :: [ 03:46:39 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_6_10_GA :: [ 03:47:14 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 03:50:21 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_7_9_GA :: [ 03:50:55 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 03:53:44 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_8_6_0_GA :: [ 03:54:33 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 03:56:44 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_9_0_0_GA :: [ 03:57:15 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 03:59:36 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_8_7_TESTING :: [ 04:00:30 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 04:02:26 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2.9 against RHEL_9_1_TESTING :: [ 04:02:57 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) ansible-core-2.13.2-1 :: [ 04:08:49 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2 against RHEL_7_9_GA :: [ 04:09:24 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 04:11:19 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2 against RHEL_8_6_0_GA :: [ 04:12:09 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 04:13:28 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2 against RHEL_9_0_0_GA :: [ 04:13:59 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 04:16:09 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2 against RHEL_8_7_TESTING :: [ 04:17:00 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0) :: [ 04:18:42 ] :: [ BEGIN ] :: Test tests_unit.yml with ANSIBLE-2 against RHEL_9_1_TESTING :: [ 04:19:14 ] :: [ PASS ] :: Test tests_unit.yml (Assert: expected 0, got 0)
Forget to mention, I was using rhel-system-roles-1.20.0-1.el8.noarch
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-2022:7568