Bug 1488358 - Slow Initialization of LLDP on failure
Summary: Slow Initialization of LLDP on failure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: SuperVDSM
Version: 4.19.30
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.6
: 4.19.31
Assignee: Dominik Holler
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-05 08:18 UTC by Dominik Holler
Modified: 2017-09-19 10:02 UTC (History)
3 users (show)

Fixed In Version: vdsm v4.19.31
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-09-19 10:02:16 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: exception+

Attachments (Terms of Use)
supervdsm.log (91.02 KB, text/plain)
2017-09-05 08:18 UTC, Dominik Holler 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81442 0 ovirt-4.1 POST net: Fail early on initialization of LLDP 2017-09-05 08:24:33 UTC

Description Dominik Holler 2017-09-05 08:18:48 UTC 
Created attachment 1322110 [details]
supervdsm.log

Description of problem:

Initialization of LLDP uses lldpad internally. The usage of lldpad/lldptool in VDSM may be slowed down by problems like #1479767 and blocks the initialization of supervdsmd. In the attached example the unsuccessful initialization took 16 seconds for three interfaces.

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

How reproducible:

Restarting supervdsmd on a system which is affected by #1479767.

Steps to Reproduce:
1. systemctl restart supervdsmd
2.
3.

Actual results:

Failing initialization may take up to four seconds per network interface.

Expected results:

Failing initialization may take up to two seconds.

Additional info:
Comment 1 Michael Burman 2017-09-10 10:44:51 UTC 
Verified on - vdsm-4.19.31-1.el7ev.x86_64
Note You need to log in before you can comment on or make changes to this bug.