Red Hat Bugzilla – Bug 854496
MTU configuration should be disabled and blocked for 3.0 DC
Last modified: 2016-02-10 15:00:05 EST
Description of problem:
The MTU support is introduced for 3.1 cluster level hosts.
Currently a user can define a network on 3.1 DC and set its MTU to differ from the default value.
The MTU check box on 'Add Logical Network' dialog should be disabled for 3.0 DC (either from DC's 'Logical Networks' sub-tab or from Cluster's 'Logical Networks' sub tab)
In addition, there backend should also block/prevent from passing MTU to vdsm for 3.0 DC level.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create DC 3.0
2. Create new logical network - check the "Override MTU" checkbox
A network with configured MTU is created for 3.0 DC.
Action should be blocked.
A suggested patch:
Disable MTU for 3.0 DC on engine side:
Disable MTU for 3.0 DC on UI:
upstream commit http://gerrit.ovirt.org/#/c/7908/5
Tested on rhevm-3.1.0-16.el6ev.noarch.
MTU checkbox is greyed out on DC level and on cluster level.
(In reply to comment #5)
> Tested on rhevm-3.1.0-16.el6ev.noarch.
> MTU checkbox is greyed out on DC level and on cluster level.
That covers the bug fix on UI side. On backend side it could be verified by adding new network via rest-api and providing an mtu for a network being added to 3.0 DC.
Tested with REST.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<detail>[Cannot add Network. Overriding MTU is not supported for this Data Center's compatibility version.]</detail>