Bug 1367483

Summary: Installing a 3.6 host to rhev-m 4.0 results in 'ovirtmgmt' network as out of sync
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.2.6CC: bugs, danken, jbelka, mmirecki, sbonazzo, ylavi
Target Milestone: ovirt-4.0.2Keywords: Regression
Target Release: 4.0.2.7Flags: rule-engine: ovirt-4.0.z+
rule-engine: blocker+
ylavi: planning_ack+
danken: devel_ack+
myakove: testing_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: 3.6 hosts do not report a switch type. Consequence: The switch type in engine is null. Fix: If 3.6 host does not report any switch type, it is considered that the host's switch type is LEGACY
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-22 12:32:03 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:

Description Michael Burman 2016-08-16 14:11:29 UTC 
Description of problem:
Installing a 3.6 host to rhev-m 4.0 results in 'ovirtmgmt' network as out of sync.

Adding a 3.6 host to rhv-m 4.0 ends up with 'ovirtmgmt' network as out-of-sync cause of the switch type value that is missing on the host. 

How reproducible:
100

Additional info:
See also - BZ 1364787
Comment 1 Yaniv Lavi 2016-08-17 15:15:52 UTC 
*** Bug 1365470 has been marked as a duplicate of this bug. ***
Comment 2 Michael Burman 2016-08-22 08:04:59 UTC 
Verified on - 4.0.2.7-0.1.el7ev and vdsm-4.17.33-1.el7ev.noarch