Bug 1510859 - Possible duplicate bridge names due VDSM name.
Summary: Possible duplicate bridge names due VDSM name.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.1.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.9
: ---
Assignee: Leon Goldberg
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-08 10:31 UTC by Leon Goldberg
Modified: 2018-01-24 10:40 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.1.9
Clone Of:
Environment:
Last Closed: 2018-01-24 10:40:13 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83760 0 ovirt-engine-4.1 MERGED backend: Add validation for network name used as vdsm name. 2017-12-11 12:07:11 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.