Bug 1890071

Summary:	Bond mode 4 is detected as custom bond options
Product:	[oVirt] ovirt-engine	Reporter:	Dominik Holler <dholler>
Component:	BLL.Network	Assignee:	Dominik Holler <dholler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.3	CC:	bugs, jarod
Target Milestone:	ovirt-4.4.4	Keywords:	Reopened
Target Release:	4.4.4	Flags:	pm-rhel: ovirt-4.4+ dholler: devel_ack+ mburman: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-21 12:36:03 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 Dominik Holler 2020-10-21 10:15:29 UTC

Description of problem:
If in Web Administration Portal a bond with mode 4 selected from the drop-down is created, the bond is detected as "Custom mode mode=4 xmit_hash_policy=2".


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


How reproducible:
100%

Steps to Reproduce:
1. Create a new bond with bonding mode "(Mode 4) Dynamic link aggregation (802.3ad)" in Admin Portal.
2. Apply changes by clicking "OK" in Setup Host Networks dialog
3. Open the Setup Host Networks dialog again and edit the previously created bond interface

Actual results:
The bond is detected as "Custom mode mode=4 xmit_hash_policy=2"

Expected results:
The bond is detected as "(Mode 4) Dynamic link aggregation (802.3ad)"

Additional info:

Comment 1 Sandro Bonazzola 2020-11-06 13:37:22 UTC

This can be tested on 4.4.3

Comment 5 Dominik Holler 2020-11-09 07:52:47 UTC

Sorry for the confusion, the fix is ovirt-engine-4.4.4 only.

Comment 6 Michael Burman 2020-11-15 09:47:38 UTC

Verified on - rhvm-4.4.4-0.1.el8ev.noarch

Comment 7 Sandro Bonazzola 2020-12-21 12:36:03 UTC

This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

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