Bug 980233 - bond as a member of a bridge and some other setups can not be handled completely
Summary: bond as a member of a bridge and some other setups can not be handled completely
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-01 19:25 UTC by Fabian Deutsch
Modified: 2013-11-11 09:59 UTC (History)
12 users (show)

Fixed In Version: ovirt-node-3.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 09:59:36 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 16505 0 None None None Never

Description Fabian Deutsch 2013-07-01 19:25:01 UTC 
Description of problem:
Due to the network rewrite many network setups are allowed, but some can still not be handled
e.g.:
* bond as a slave of a bridge
* tagged bond as a slave of a bridge
Comment 1 Fabian Deutsch 2013-07-04 14:49:28 UTC 
The logic has been updated.

All supported layouts are now discovered.
The discovery is based on the central configuration file. So only if the configuration happened through Node the setup will be discovered and displayed correctly.

There is some best effort for other arbitrary setups.

Unittests were added which ensure that every setup we can create is also discovered correctly.
Comment 2 Sandro Bonazzola 2013-11-11 07:32:35 UTC 
oVirt gerrit 16505 is merged, can you set target release, fixed in version and move this to modified/on qa/closed accordingly?
Note You need to log in before you can comment on or make changes to this bug.