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:
[root@wsfd-netdev34-vm-8 ~]# a=0; while nmcli networking on && sleep 1 && nmcli networking off && sleep 1; do :;((a++)); echo "ATTEMPT $a" ; done; nmcli networking on

ATTEMPT 13
Error: failed to set networking: Timeout was reached

ATTEMPT 69
Error: failed to set networking: Timeout was reached

ATTEMPT 51
Error: failed to set networking: Timeout was reached

ATTEMPT 18
Error: failed to set networking: Timeout was reached

so we can see timeout here and there.

Version-Release number of selected component (if applicable):
NetworkManager-1.43.10-1.el9.x86_64

How reproducible:
always

Steps to Reproduce:
1. run above mentioned command 

Actual results:
timeout in a while

Expected results:
no timeout

Additional info:

Hi Vladimir Benes,

I failed to reproduced it in my VM using `NetworkManager-1.43.10-1.el9.x86_64` with 100 VLANs and 100 linux bridges.

Can you provide trace log of NM or a server which can reproduce this problem?

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days