Bug 1788081

Summary: libnm timeout on create vlans
Product: Red Hat Enterprise Linux 8 Reporter: eraviv
Component: nmstateAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: dholler, fge, jiji, jishi, network-qe, till
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.2   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.2.5-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:00:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1766193    
Attachments:
Description Flags
vdsm.log
none
supervdsm.log
none
Desired state from the supervdsm.log none

Description eraviv 2020-01-06 10:48:21 UTC
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.

Comment 1 eraviv 2020-01-06 10:49:19 UTC
Created attachment 1650083 [details]
supervdsm.log

Comment 2 Till Maas 2020-01-09 20:13:59 UTC
Created attachment 1651065 [details]
Desired state from the supervdsm.log

Comment 7 errata-xmlrpc 2020-04-28 16:00:37 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, 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