Back to bug 1043808

Who When What Removed Added
Jaison Raju 2013-12-17 09:29:28 UTC CC jraju
Jaison Raju 2013-12-17 09:29:48 UTC Summary For an interface with multiple VLAN interfaces, rhev Host assigns highest mtu of a vlan interface to all vlan interface under the interfaces . For an interface with multiple VLAN interfaces, rhev Host assigns highest mtu of a vlan interface to all vlan interface under the interface .
Jaison Raju 2013-12-17 09:30:12 UTC Summary For an interface with multiple VLAN interfaces, rhev Host assigns highest mtu of a vlan interface to all vlan interface under the interface . For an interface with multiple VLAN interfaces, rhev Host assigns highest mtu of a vlan interface to all vlan interface under the parent interface .
Oved Ourfali 2013-12-17 11:39:41 UTC Keywords FutureFeature
Whiteboard network
Red Hat Bugzilla 2013-12-17 11:39:41 UTC Doc Type Bug Fix Enhancement
Nir Yechiel 2013-12-18 08:38:20 UTC CC nyechiel
Itamar Heim 2013-12-29 09:03:35 UTC Keywords FutureFeature
CC Rhev-m-bugs
Component RFEs ovirt-engine-backend
Assignee acathrow nobody
QA Contact srevivo
Red Hat Bugzilla 2013-12-29 09:03:35 UTC Doc Type Enhancement Bug Fix
Ayal Baron 2014-01-01 08:12:56 UTC CC abaron
RHEL Program Management 2014-01-01 15:59:42 UTC Target Release --- 3.4.0
Dan Kenigsberg 2014-01-05 11:21:04 UTC CC danken
Flags needinfo?(jraju)
lpeer 2014-01-05 11:29:52 UTC CC abaron, bazulay, hateya
Component ovirt-engine-backend vdsm
Assignee nobody danken
Dan Kenigsberg 2014-01-06 13:42:09 UTC CC masayag
Flags needinfo?(jraju) needinfo?(masayag)
Moti Asayag 2014-01-06 14:00:22 UTC Flags needinfo?(masayag)
Dan Kenigsberg 2014-01-06 15:51:01 UTC Flags needinfo?(masayag)
Meni Yakove 2014-01-07 08:33:46 UTC Keywords Triaged
CC myakove
John Skeoch 2014-01-13 01:19:17 UTC CC hateya
Shai Revivo 2014-01-26 11:37:22 UTC Keywords Triaged
Dan Kenigsberg 2014-02-03 16:11:12 UTC Target Release 3.4.0 3.5.0
Moti Asayag 2014-02-04 14:19:16 UTC Flags needinfo?(masayag)
Moti Asayag 2014-03-03 10:09:50 UTC CC gklein
Component vdsm ovirt-engine-backend
Assignee danken masayag
QA Contact myakove
Moti Asayag 2014-03-09 21:40:53 UTC Assignee masayag nobody
John Skeoch 2014-03-17 02:03:13 UTC CC abaron
Moti Asayag 2014-05-02 09:30:36 UTC Assignee nobody alkaplan
Alona Kaplan 2014-05-26 09:32:31 UTC Status NEW POST
Alona Kaplan 2014-07-09 08:33:03 UTC Status POST MODIFIED
Eyal Edri 2014-07-13 14:12:45 UTC Status MODIFIED ON_QA
Fixed In Version vt1.3
Meni Yakove 2014-07-17 06:50:54 UTC Status ON_QA VERIFIED
John Skeoch 2014-09-07 23:16:24 UTC CC acathrow rbalakri
Joe Donohue 2014-09-18 12:49:56 UTC Blocks 1142923
Joe Donohue 2014-10-23 17:36:46 UTC Blocks 1156162
Joe Donohue 2014-10-23 17:39:55 UTC Blocks 1156165
Joe Donohue 2014-10-23 17:42:09 UTC Blocks 1156162
Lior Vernia 2014-11-30 09:48:27 UTC CC alkaplan, lvernia
Flags needinfo?(alkaplan)
Alona Kaplan 2014-11-30 12:00:50 UTC Environment Moving the setting of the actual (host level) value of a default mtu to the engine side.
DefaultMTU config value was added to the engine.
Networks that are marked as default by the gui or set mtu=0 by the rest api will get DefaultMTU value when attached to a host.
A network that is marked to have default mtu (on the data center level), but in fact its mtu on the host is different than DefaultMTU, will be marked as unsync.

Please notice- when upgrading the engine to 3.5, all the networks with default MTU (on the dc level), which the actual mtu (host level) set on them is different than DefaultMTU config value will be marked as out-of-sync.
Flags needinfo?(alkaplan)
Alona Kaplan 2014-11-30 12:08:16 UTC Environment Moving the setting of the actual (host level) value of a default mtu to the engine side.
DefaultMTU config value was added to the engine.
Networks that are marked as default by the gui or set mtu=0 by the rest api will get DefaultMTU value when attached to a host.
A network that is marked to have default mtu (on the data center level), but in fact its mtu on the host is different than DefaultMTU, will be marked as unsync.

Please notice- when upgrading the engine to 3.5, all the networks with default MTU (on the dc level), which the actual mtu (host level) set on them is different than DefaultMTU config value will be marked as out-of-sync.
Doc Text Moving the setting of the actual (host level) value of a default mtu to the engine side.
DefaultMTU config value was added to the engine.
Networks that are marked as default by the gui or set mtu=0 by the rest api will get DefaultMTU value when attached to a host.
A network that is marked to have default mtu (on the data center level), but in fact its mtu on the host is different than DefaultMTU, will be marked as unsync.

Please notice- when upgrading the engine to 3.5, all the networks with default MTU (on the dc level), which the actual mtu (host level) set on them is different than DefaultMTU config value will be marked as out-of-sync.
Julie 2014-12-01 06:13:17 UTC CC juwu
Doc Text Moving the setting of the actual (host level) value of a default mtu to the engine side.
DefaultMTU config value was added to the engine.
Networks that are marked as default by the gui or set mtu=0 by the rest api will get DefaultMTU value when attached to a host.
A network that is marked to have default mtu (on the data center level), but in fact its mtu on the host is different than DefaultMTU, will be marked as unsync.

Please notice- when upgrading the engine to 3.5, all the networks with default MTU (on the dc level), which the actual mtu (host level) set on them is different than DefaultMTU config value will be marked as out-of-sync.
Previously, for an host interface that has multiple VLAN interfaces, the highest MTU available was assigned to all vlan interfaces under that interface, and caused the host going into a non-responsive state. This bug fix moves the setting of the host level value of a default MTU to the engine side so a default value is in place if the MTU is not manually set. Also note that the default host level MTU must be the same as the data center level MTU, otherwise the network is considered out of synchronization.
Flags needinfo?(alkaplan)
Alona Kaplan 2014-12-01 06:42:21 UTC Flags needinfo?(alkaplan) needinfo?(juwu)
Julie 2014-12-01 07:04:11 UTC Flags needinfo?(juwu)
Alona Kaplan 2014-12-01 07:24:43 UTC Flags needinfo?(juwu)
Julie 2014-12-01 08:40:17 UTC Doc Text Previously, for an host interface that has multiple VLAN interfaces, the highest MTU available was assigned to all vlan interfaces under that interface, and caused the host going into a non-responsive state. This bug fix moves the setting of the host level value of a default MTU to the engine side so a default value is in place if the MTU is not manually set. Also note that the default host level MTU must be the same as the data center level MTU, otherwise the network is considered out of synchronization. Previously, for an host interface that has multiple VLAN interfaces, the highest MTU available was assigned to all vlan interfaces under that interface, and caused the host going into a non-responsive state. This bug fix moves the setting of the host level value of a default MTU to the engine side so a default value is in place if the MTU is not manually set. You can set the default MTU by setting the 'DefaultMTU' property using the engine-config tool. The default host level MTU must be the same as the data center level MTU, otherwise the network is considered out of synchronization. After upgrading to Red Hat Enterprise Virtrualization 3.5, if the host level and the data center level MTU is not the same, the network will be out of synchronization.
Flags needinfo?(juwu)
Julie 2014-12-03 23:28:03 UTC Doc Text Previously, for an host interface that has multiple VLAN interfaces, the highest MTU available was assigned to all vlan interfaces under that interface, and caused the host going into a non-responsive state. This bug fix moves the setting of the host level value of a default MTU to the engine side so a default value is in place if the MTU is not manually set. You can set the default MTU by setting the 'DefaultMTU' property using the engine-config tool. The default host level MTU must be the same as the data center level MTU, otherwise the network is considered out of synchronization. After upgrading to Red Hat Enterprise Virtrualization 3.5, if the host level and the data center level MTU is not the same, the network will be out of synchronization. Previously, for an host interface that has multiple VLAN interfaces, the highest MTU available was assigned to all VLAN interfaces under that interface, and caused the host going into a non-responsive state. This bug fix moves the setting of the host level value of a default MTU to the engine side so a default value is in place if the MTU is not manually set. You can set the default MTU by setting the 'DefaultMTU' property using the engine-config tool. The default host level MTU must be the same as the data center level MTU, otherwise the network is considered out of synchronization. After upgrading to Red Hat Enterprise Virtrualization 3.5, if the host level and the data center level MTU is not the same, the network will be out of synchronization.
Yaniv Lavi 2014-12-08 15:26:07 UTC Group rhev, qa, support, private, devel
Scott Herold 2014-12-22 14:45:02 UTC Group redhat
CC sherold
errata-xmlrpc 2015-02-11 15:35:59 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2015-02-11 17:56:52 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2015-02-11 12:56:52 UTC
Yaniv Lavi 2016-02-10 19:55:51 UTC oVirt Team --- Network
Gil Klein 2019-04-28 09:44:58 UTC CC gklein

Back to bug 1043808