Bug 1510859

Summary:	Possible duplicate bridge names due VDSM name.
Product:	[oVirt] ovirt-engine	Reporter:	Leon Goldberg <lgoldber>
Component:	BLL.Network	Assignee:	Leon Goldberg <lgoldber>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.0.2	CC:	bugs, danken, lgoldber, lveyde, mburman, tnisan
Target Milestone:	ovirt-4.1.9	Flags:	rule-engine: ovirt-4.1+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.1.9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-24 10:40:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Leon Goldberg 2017-11-08 10:31:46 UTC

In a scenario where a network is named with an already existing VDSM name, if the network is attached to a host already attached with a network with the same (VDSM) name, a collision will occur.

Comment 1 Dan Kenigsberg 2017-11-23 19:41:36 UTC

Too bad, we've missed the deadline for 4.1.8.

Comment 2 Michael Burman 2018-01-14 13:53:33 UTC

Hi Leon,

We don't know how test this report, please provide us clear steps or help us to verify this bug. Thanks,

Comment 3 Leon Goldberg 2018-01-14 14:09:16 UTC

- Create a network with a long name
- Check what is the generated VDSM name
- Attempt to create a network with the VDSM name as its name

Comment 4 Michael Burman 2018-01-14 14:50:24 UTC

Thanks Leon,

Verified on - 4.2.1.1-0.1.el7

If trying to create a logical network with the vdsm name which already exist as vdsm name on the host, we will fail with:

'Error while executing action: Bad network name (ona390df1161de4). The name is already used as an on-host identifier of the network: qwertyuiopasdfgh'

Comment 5 Michael Burman 2018-01-14 14:53:35 UTC

Verified on -  4.1.9-0.2.el7

Comment 6 Sandro Bonazzola 2018-01-24 10:40:13 UTC

This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.