Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 842986

Summary: Wrong boot protocol for non-VLANed non-bridged networks
Product: Red Hat Enterprise Virtualization Manager Reporter: Igor Lvovsky <ilvovsky>
Component: ovirt-engineAssignee: Moti Asayag <masayag>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: alkaplan, dyasny, ecohen, iheim, lpeer, masayag, mavital, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Network
Fixed In Version: si13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 19:58:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 843498    
Bug Blocks:    

Description Igor Lvovsky 2012-07-25 08:32:02 UTC
Description of problem:

Attach non-VLANed non-bridged network to interface and set boot protocol to static with IP and netmask.
The setupNetwork will get the parameters and action will be performed successfully.
But, if we will open edit network screen again, we will see IP and netmask fields greyed-out (with proper parameters inside) and boot protocol will back to None

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 GenadiC 2012-07-25 11:54:58 UTC
Another scenario: When you configure VLAN Network over the bond, the boot protocol will be None as well, even when you change the protocol to DHCP or static

Comment 2 Igor Lvovsky 2012-07-25 15:03:50 UTC
It happens only on bridgeless (VLAN or non-VLAN) network, without any relation to the bond

Comment 3 Igor Lvovsky 2012-07-25 15:05:02 UTC
According to Moti the cause of this is absent of 'cfg' field in getVdsCaps for bridgeless networks.

Comment 7 Meni Yakove 2012-08-05 07:58:24 UTC
Verified on vdsm-4.9.6-26.0.el6_3.x86_64.