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

Bug 1242235

Summary: [New HostSetupNetworksCommand] Marking ipConfiguration and overridden QoS as out-of-sync
Product: [oVirt] ovirt-engine Reporter: Alona Kaplan <alkaplan>
Component: GeneralAssignee: Eliraz Levi <elevi>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: high    
Version: ---CC: bazulay, bugs, danken, ecohen, gcheresh, gklein, lsurette, rbalakri, yeylon, ylavi
Target Milestone: ovirt-3.6.0-rcKeywords: Regression
Target Release: 3.6.0Flags: rule-engine: ovirt-3.6.0+
rule-engine: blocker+
ylavi: Triaged+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:41:45 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:
Bug Depends On: 1043226, 1184497    
Bug Blocks:    

Description Alona Kaplan 2015-07-12 12:50:06 UTC
Description of problem:

In the old setup networks api there was the ability to see if the following properties are out-of-sync ('out-of-sync'=the logical network/host network qos has different values than the host reported interface- vdsNetworkInterface)- mtu, vlan and QoS (outAverageLinkshare, outAverageUpperlimit and outAverageRealtime).

The new HostSetupNetworks api introduces new entity- NetworkAttachment, which allows tracking also the sync status of the following properties-  
IpConfiguration (boot protocol, ip address, netmask/prefix and gateway) and
overriden QoS.

However, the current code (engine and ui) still doesn't support showing the sync status of those properties.

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


How reproducible:
100%

Steps to Reproduce:
1. Change the 'ip' of a network via the host
2. Mark the qos of the host network as overridden-> change the 'outAverageLinkshare' manually on the host
3. Call refresh caps

Actual results:
The 'ip' and 'outAverageLinkshare' are not marked as 'out-of-sync'.

Expected results:
The 'ip' and 'outAverageLinkshare' are marked as 'out-of-sync'.

Additional info:

Comment 1 Michael Burman 2015-10-12 07:41:01 UTC
Tested and verified on - 3.6.0-0.18.el6 with vdsm-4.17.8-1.el7ev.noarch

Difference recognized between Host and DC when changing manually network properties on host -->
Host Qos (with tc command)
Bootproto(with vdsClient setup networks command)
IP
Netmask 

This properties marked as out-of-sync ^^

- For gateway change on host i opened a separate BZ 1270688

Comment 2 Sandro Bonazzola 2015-11-04 11:41:45 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.