Bug 1554268 - report openstack_binding_host_ids on vdsm caps
Summary: report openstack_binding_host_ids on vdsm caps
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.20.19
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Dan Kenigsberg
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks: 1549030
TreeView+ depends on / blocked
 
Reported: 2018-03-12 09:33 UTC by Dan Kenigsberg
Modified: 2018-03-29 11:15 UTC (History)
6 users (show)

Fixed In Version: vdsm v4.20.22
Clone Of: 1549030
Environment:
Last Closed: 2018-03-29 11:15:33 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87913 0 ovirt-4.2 MERGED openstack_net hook: drop ancient security group logic 2018-03-12 16:00:55 UTC
oVirt gerrit 87914 0 ovirt-4.2 MERGED openstack_net hook: report neutron names of host 2018-03-12 16:01:00 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.