RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1918252 - [network-role] Test tests_bond_nm.yml failed when checking interface after created
Summary: [network-role] Test tests_bond_nm.yml failed when checking interface after cr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.5
Assignee: Gris Ge
QA Contact: Zhiqian Guan
URL:
Whiteboard: role:network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-20 10:32 UTC by Zhiqian Guan
Modified: 2021-11-09 20:28 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.6.4-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 17:44:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles network pull 399 0 None closed test: Fix the bond test on DHCP 2021-07-28 20:51:43 UTC
Github linux-system-roles network pull 408 0 None closed CI: Enable integration test in Github Action 2021-07-28 20:51:56 UTC
Red Hat Product Errata RHBA-2021:4159 0 None None None 2021-11-09 17:45:14 UTC

Description Zhiqian Guan 2021-01-20 10:32:16 UTC 
Description of problem:
After creating the bond interface using the linux-system-role.network role, we use a command "ip -4 a s {{ master_device }}" to check the interface status and info. But the check was failed.

Detail log: https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2021/01/49970/4997086/9411618/120450241/SYSTEM-ROLE-network_tests_bond_nm.yml-ANSIBLE-2.8-RHEL_8_4_0_BETA.log

Version-Release number of selected component (if applicable):
Ansible 2.8/2.9 in RHEL8.4

How reproducible:
always

Steps to Reproduce:
1.Run tests_bond_nm.yml test playbook in 8.4

Actual results:
Failed result

Expected results:
Test pass
Additional info:
Comment 3 Rich Megginson 2021-05-18 17:02:20 UTC 
I cannot reproduce - this is what I tried:

1minutetip -p ANSIBLE_VER=2.8 -p SYSTEM_ROLES_ONLY_TESTS=tests_bond_nm 1MT-RHEL-8.4.0-20210503.1

This used the latest rhel 8.4, the latest rhel-system-roles-1.0.1 in rhel 8.4, and ansible 2.8

The log is attached

Can you reproduce?
Comment 5 Zhiqian Guan 2021-05-19 06:02:16 UTC 
Yes, I can still reproduce this on a beaker job, but it seems not 100% reproducible.

https://beaker.engineering.redhat.com/recipes/10006581#tasks

You can see the first upstream-test suite is using ansible 2.8, and the last two tasks are using ansible 2.9. The first test of 2.9 successed, but the second one failed.

The rhel-system-role version is: rhel-system-roles-1.0.1-1.el8.noarch

Error:
TASK [** TEST check IPv4] ******************************************************
task path: /tmp/tmp.SQCEuT9pPm/roles/rhel-system-roles.network/tests/playbooks/tests_bond.yml:72
FAILED - RETRYING: ** TEST check IPv4 (20 retries left).
FAILED - RETRYING: ** TEST check IPv4 (19 retries left).
FAILED - RETRYING: ** TEST check IPv4 (18 retries left).
FAILED - RETRYING: ** TEST check IPv4 (17 retries left).
FAILED - RETRYING: ** TEST check IPv4 (16 retries left).
FAILED - RETRYING: ** TEST check IPv4 (15 retries left).
FAILED - RETRYING: ** TEST check IPv4 (14 retries left).
FAILED - RETRYING: ** TEST check IPv4 (13 retries left).
FAILED - RETRYING: ** TEST check IPv4 (12 retries left).
FAILED - RETRYING: ** TEST check IPv4 (11 retries left).
FAILED - RETRYING: ** TEST check IPv4 (10 retries left).
FAILED - RETRYING: ** TEST check IPv4 (9 retries left).
FAILED - RETRYING: ** TEST check IPv4 (8 retries left).
FAILED - RETRYING: ** TEST check IPv4 (7 retries left).
FAILED - RETRYING: ** TEST check IPv4 (6 retries left).
FAILED - RETRYING: ** TEST check IPv4 (5 retries left).
FAILED - RETRYING: ** TEST check IPv4 (4 retries left).
FAILED - RETRYING: ** TEST check IPv4 (3 retries left).
FAILED - RETRYING: ** TEST check IPv4 (2 retries left).
FAILED - RETRYING: ** TEST check IPv4 (1 retries left).
fatal: [image.qcow2]: FAILED! => {"attempts": 20, "changed": true, "cmd": ["ip", "-4", "a", "s", "nm-bond"], "delta": "0:00:00.002447", "end": "2021-05-19 00:18:20.007534", "rc": 0, "start": "2021-05-19 00:18:20.005087", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
Comment 9 Gris Ge 2021-07-14 14:21:03 UTC 
Patch send to upstream for review: https://github.com/linux-system-roles/network/pull/399
Comment 16 Zhiqian Guan 2021-08-09 04:22:37 UTC 
[root@netqe2 Upstream-testsuite]# rpm -q rhel-system-roles
rhel-system-roles-1.6.6-1.el8.noarch
[root@netqe2 Upstream-testsuite]#
:: [ 00:06:09 ] :: [   PASS   ] :: Test network/tests_bond_nm.yml (roles/rhel-system-roles.network/tests/tests_bond_nm.yml) with ANSIBLE-2.9 against RHEL_6_10_GA (Expected 0, got 0)
:: [ 00:08:57 ] :: [   PASS   ] :: Test network/tests_bond_nm.yml (roles/rhel-system-roles.network/tests/tests_bond_nm.yml) with ANSIBLE-2.9 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 00:11:26 ] :: [   PASS   ] :: Test network/tests_bond_nm.yml (roles/rhel-system-roles.network/tests/tests_bond_nm.yml) with ANSIBLE-2.9 against RHEL_8_4_0_GA (Expected 0, got 0)
:: [ 00:13:25 ] :: [   PASS   ] :: Test network/tests_bond_nm.yml (roles/rhel-system-roles.network/tests/tests_bond_nm.yml) with ANSIBLE-2.9 against RHEL_8_5_0_TESTING (Expected 0, got 0)
:: [ 00:15:39 ] :: [   PASS   ] :: Test network/tests_bond_nm.yml (roles/rhel-system-roles.network/tests/tests_bond_nm.yml) with ANSIBLE-2.9 against RHEL_9_TESTING (Expected 0, got 0)
Comment 18 Zhiqian Guan 2021-08-09 04:27:03 UTC 
Based on Comment16 and comment17, set this to VERIFIED
Comment 20 errata-xmlrpc 2021-11-09 17:44:47 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-2021:4159
Note You need to log in before you can comment on or make changes to this bug.