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.

Created attachment 1650082 [details]
vdsm.log

Description of problem:
not all vlans are created when submitting a large batch of them to nmstate.
libnm reports a timeout.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. create 150 vlans with the same label on a RHV datacenter
2. add a host to the datacenter
3. open the setup networks dialog for the above host
4. on a non-ovirtmgmt nic of the host, apply the label


Actual results:
RHV reports internal error
most of the vlans are not created on the nic

Expected results:
all vlans should be created

Additional info:
according to the logs, it looks like libnm enforces a timeout of 35 seconds on a job, and drops the job when the timeout is reached.

Created attachment 1650083 [details]
supervdsm.log

Created attachment 1651065 [details]
Desired state from the supervdsm.log

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, 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-2020:1696