Bug 1008999

Summary: Gateway field can be updated for non-rhevm network on 3.2 and 3.1 Cluster and it should not exist on such a Cluster
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: ovirt-engine-webadmin-portalAssignee: Lior Vernia <lvernia>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.3.0CC: acathrow, bazulay, danken, ecohen, iheim, myakove, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: is18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description GenadiC 2013-09-17 13:16:10 UTC 
Description of problem:
If you create 3.2 or 3.1 Cluster and try to attach network to the host on that Cluster the gateway field is visible and could be updated when it shouldn't

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


How reproducible:
Always

Steps to Reproduce:
1. Create Cluster 3.2
2. Add host and attach network (other than rhevm) with SetupNetworks
3.

Actual results:
You can configure gateway for that network

Expected results:
Gateway field should not exist for non-rhevm network

Additional info:
Comment 1 Meni Yakove 2013-10-10 08:45:29 UTC 
rhevm-3.3.0-0.25.beta1.el6ev.noarch
Comment 2 Itamar Heim 2014-01-21 22:27:26 UTC 
Closing - RHEV 3.3 Released
Comment 3 Itamar Heim 2014-01-21 22:27:44 UTC 
Closing - RHEV 3.3 Released
Comment 4 Itamar Heim 2014-01-21 22:30:33 UTC 
Closing - RHEV 3.3 Released