Bug 1269096

Summary: Unable to successfully add [v 3.6] host to [v 3.5] engine fails during host installation.
Product: Red Hat Enterprise Virtualization Manager Reporter: mlehrer
Component: vdsmAssignee: Eliraz Levi <elevi>
Status: CLOSED NOTABUG QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: bazulay, cwu, danken, ecohen, gklein, lsurette, lsvaty, mlehrer, pstehlik, ycui, yeylon, ylavi
Target Milestone: ovirt-3.6.1   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 11:26: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:
Attachments:
Description Flags
Log of host deploy failure none

Description mlehrer 2015-10-06 10:43:40 UTC
Created attachment 1080198 [details]
Log of host deploy failure

Description of problem:

Attempt to add 3.6 host to 3.5 engine fails during host setup with the following error 
 "failed to configure management on the host", also " the following networks are missing on the host" rhevm"

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

vdsm-4.17.6-1.el7ev.noarch

How reproducible:
Set up 3.5 engine.
Attempt to add host configured with 3.6


Steps to Reproduce:
1.
2.
3.

Actual results:

Unable to deploy host.

Expected results:

To be able to successfully deploy host.

Additional info:

Comment 1 Yaniv Kaul 2015-10-08 08:36:46 UTC
Is it 3.5.0, 3.5.4, 3.5.5? or doesn't matter and the issue is in the VDSM 3.6 side (and therefore the 'version' field should be 3.6) ?

Comment 2 Dan Kenigsberg 2015-10-18 09:39:56 UTC
Please provide engine version, engine.log, and {super,}vdsm.log. The currently-attached ovirt-host-deploy.log shows no failure afaict.

Comment 3 Yaniv Lavi 2015-10-21 09:34:37 UTC
Did you test this flow in 3.6? does it work?

Comment 4 Lukas Svaty 2015-10-21 10:04:19 UTC
reproducible, adding 3.6 host to rhevm-3.5.5-0.1.el6ev.noarch

Comment 5 Lukas Svaty 2015-10-21 10:06:57 UTC
by removing 'ovirtmgmnt' bridge and adding correct 'rhevm' bridge on host will enable 3.6 hosts inside 3.5.5 engine

Comment 6 Yaniv Kaul 2015-10-21 10:11:10 UTC
Lukas, can you please add logs, per comment 2 above?

Comment 8 Lukas Svaty 2015-10-21 11:57:04 UTC
The issue is in bridge through which vdsm connects to hosts. In older version of RHEV-M we used rhevm bridge as a default network connection. In oVirt and RHEV-M-3.6 we use ovirtmgmt bridge. As during host deployment vdsm is unable to attach rhevm bridge to the correct network interface (as it has already a ovirtmgmt bridge) it fails on setup.

Previously I saw some bugs in the past about resolution of default bridge naming, as it should have been moved to ovirtmgmt in oVirt as well as RHEV-M. Do you know what was the resolution in this issue? If we are using different network bridge for oVirt and RHEV-M or it was decided they will be the same?

Comment 9 Dan Kenigsberg 2015-10-21 14:46:19 UTC
What has created the ovirtmgmt bridge on your host?

We do not support adding a host with one management network name into a cluster with another name. Please confirm that prior to deployment, no bridge existed on the host.

Comment 10 mlehrer 2015-10-22 07:25:36 UTC
(In reply to Yaniv Kaul from comment #1)
> Is it 3.5.0, 3.5.4, 3.5.5? or doesn't matter and the issue is in the VDSM
> 3.6 side (and therefore the 'version' field should be 3.6) ?

The environment was used for a different scale bug, and is no longer available.

Comment 11 mlehrer 2015-10-22 07:26:17 UTC
(In reply to Yaniv Kaul from comment #1)
> Is it 3.5.0, 3.5.4, 3.5.5? or doesn't matter and the issue is in the VDSM
> 3.6 side (and therefore the 'version' field should be 3.6) ?

The environment was used for a different scale bug, and is no longer available.

Comment 12 Lukas Svaty 2015-10-22 08:54:43 UTC
ovirtmgmt bridge on host was created by 3.6 engine where host was previously added

Problem is we have different bridges for rhevm-3.5 (rhevm) and rhevm-3.6 (ovirtmgmt).

As mentioned in comment#5 these steps works, so the issue is only in the name of bridge:

1. Remove host from 3.6 engine
2. Remove ovirtmgmt bridge from host
3. Add host to 3.5 engine (which will create rhevm bridge)

Comment 13 Dan Kenigsberg 2015-10-22 11:26:45 UTC
(In reply to Lukas Svaty from comment #12)

> Problem is we have different bridges for rhevm-3.5 (rhevm) and rhevm-3.6
> (ovirtmgmt).

The default bridge name has intentionally changed in 3.6. Cf. bug 1204793.

Comment 14 Lukas Svaty 2015-10-22 11:39:14 UTC
I agree that this indeed is not a but, but by design behaviour, so we will be able to move hosts from ovirt to rhevm and so on.