Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
when running this two times I see nm-critical assertion:
nmcli con del team0 team-slave-eth5
nmcli con down testeth5
nmcli con add type team ifname nm-team con-name team0 config '{"runner": {"name": "lacp"}, "link_watch": {"name": "ethtool"}}' ipv4.method disable ipv6.method ignore
nmcli con add type ethernet con-name team-slave-eth5 ifname eth5
nmcli con up team-slave-eth5
sleep 1
systemctl restart NetworkManager
sleep 1
nmcli con up testeth5
Version-Release number of selected component (if applicable):
NetworkManager-1.36.0-4.el9_0.x86_64
NetworkManager-1.39.5-1.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. see above
Actual results:
(process:322457): nm-CRITICAL **: 04:51:44.278: ((src/libnm-client-impl/nm-remote-connection.c:593)): assertion '<dropped>' failed
Expected results:
no assert
Additional info:
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 (NetworkManager 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:8265
Description of problem: when running this two times I see nm-critical assertion: nmcli con del team0 team-slave-eth5 nmcli con down testeth5 nmcli con add type team ifname nm-team con-name team0 config '{"runner": {"name": "lacp"}, "link_watch": {"name": "ethtool"}}' ipv4.method disable ipv6.method ignore nmcli con add type ethernet con-name team-slave-eth5 ifname eth5 nmcli con up team-slave-eth5 sleep 1 systemctl restart NetworkManager sleep 1 nmcli con up testeth5 Version-Release number of selected component (if applicable): NetworkManager-1.36.0-4.el9_0.x86_64 NetworkManager-1.39.5-1.el9.x86_64 How reproducible: always Steps to Reproduce: 1. see above Actual results: (process:322457): nm-CRITICAL **: 04:51:44.278: ((src/libnm-client-impl/nm-remote-connection.c:593)): assertion '<dropped>' failed Expected results: no assert Additional info: