Bug 1125175

Summary:	Adding 'DefaultMtu' to engine-config
Product:	[Retired] oVirt	Reporter:	Alona Kaplan <alkaplan>
Component:	ovirt-engine-core	Assignee:	Alona Kaplan <alkaplan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	ecohen, gklein, iheim, lvernia, myakove, rbalakri, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	ovirt-3.5.0_rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:38:56 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 Alona Kaplan 2014-07-31 08:55:11 UTC

Description of problem:
There is no ability to configure 'DefaultMtu' config value via engine-config tool.


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


How reproducible:
100%

Steps to Reproduce:
1. ~/ovirt-engine/bin/engine-config -s "DefaultMtu=150"

Actual results:
"Error setting DefaultMtu's value. No such entry."

Expected results:
'DefaultMtu' value is updated to 80 in vdc_options table.

Additional info:

Comment 1 Meni Yakove 2014-09-14 06:59:26 UTC

rhevm-3.5.0-0.12.beta.el6ev.noarch

Comment 2 Sandro Bonazzola 2014-10-17 12:38:56 UTC

oVirt 3.5 has been released and should include the fix for this issue.