Bug 1554268

Summary:	report openstack_binding_host_ids on vdsm caps
Product:	[oVirt] vdsm	Reporter:	Dan Kenigsberg <danken>
Component:	General	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.20.19	CC:	bugs, lveyde, mburman, mmirecki, myakove, ylavi
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	vdsm v4.20.22	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1549030	Environment:
Last Closed:	2018-03-29 11:15:33 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:
Bug Blocks:	1549030

Description Dan Kenigsberg 2018-03-12 09:33:51 UTC

Engine depends on provider-specific host_id in order to update external network providers about the new position of a VM.

This is required for Bug #1549030.

Comment 1 Dan Kenigsberg 2018-03-14 08:46:46 UTC

To verify, run `vdsm-client Host getCapabilities` and look for openstack_binding_host_ids. An OVN host should report one value there; an OpenStack host should report another value; a host without external networks should report none. No functional change should occur.

Comment 2 Michael Burman 2018-03-19 07:08:39 UTC

"openstack_binding_host_ids": {
        "OVIRT_PROVIDER_OVN": "3694b97d-61f9-4d8f-82c4-82e75973e008"
 
For OVN host

"openstack_binding_host_ids": {
        "OPEN_VSWITCH": "rhv-1.localdomain", 

For OpenStack host 

Verified on vdsm-4.20.22-1.el7ev.x86_64

Comment 3 Sandro Bonazzola 2018-03-29 11:15:33 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.