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

Bug 1704350

Summary: Test neutron integration with RDO Stein or newer
Product: [oVirt] ovirt-engine Reporter: Sandro Bonazzola <sbonazzo>
Component: BLL.NetworkAssignee: Evgeny Slutsky <eslutsky>
Status: CLOSED CURRENTRELEASE QA Contact: Evgeny Slutsky <eslutsky>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.3.6CC: bugs, dholler, eslutsky, mavital
Target Milestone: ovirt-4.4.2Keywords: TestOnly
Target Release: ---Flags: pm-rhel: ovirt-4.4+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhv-4.4.0-28 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-18 07:11:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: External RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
terminal log of openstack installation and check none

Description Sandro Bonazzola 2019-04-29 15:36:04 UTC
RDO Stein has been released: https://blogs.rdoproject.org/2019/04/rdo-stein-released/

We should ensure that Neutron integration still works.
Tentatively targeting 4.3.4 since Stein is already out.

Neutron is reported as external provider in official documentation at https://ovirt.org/documentation/admin-guide/chap-External_Providers.html

Comment 4 Evgeny Slutsky 2019-08-15 12:43:44 UTC
in openstack Stein  Identity API v2 is deprecated (https://docs.openstack.org/keystone/stein/contributor/http-api.html)
engine support only keystone API v2, so it doesn't work with Keystone V3.

so it's impossible to use Neutron Stein with oVirt engine.

Comment 5 Dominik Holler 2019-09-10 10:53:17 UTC
(In reply to Evgeny Slutsky from comment #4)
> in openstack Stein  Identity API v2 is deprecated
> (https://docs.openstack.org/keystone/stein/contributor/http-api.html)
> engine support only keystone API v2, so it doesn't work with Keystone V3.
> 

Support for keystone API v3 for external networks was added in ovirt-4.2.7
(bug 1598391)

> so it's impossible to use Neutron Stein with oVirt engine.

It is worth to try.

Comment 6 Sandro Bonazzola 2019-09-16 07:28:37 UTC
Evgeny can you re-test? looks like v3 should work for Neutron.

Comment 7 Evgeny Slutsky 2019-09-16 14:37:06 UTC
Hi,
I've tested it again and is does work with APIv3.
the first time when tested  i've selected "External network provider" and it supported v2 only,
when selecting "Openstack Networking" it support V3 only - which is OK.

Comment 8 Dominik Holler 2019-09-18 16:37:48 UTC
Created attachment 1616304 [details]
terminal log of openstack installation and check

In the attached file is documented how I checked RDO Stein Neutron OVN with GENEVE tunnels on ovirt-4.3.
Please fine the steps I did only graphical in
https://drive.google.com/file/d/16bJt3YhnlNyZzB89ozcLrHFsmpDAQqOH/view?usp=sharing

I deployed via packstack, but I would be happy to learn how to do this with TripleO.

Comment 9 Evgeny Slutsky 2019-09-18 18:00:15 UTC
(In reply to Dominik Holler from comment #8)
> Created attachment 1616304 [details]
> terminal log of openstack installation and check
> 
> In the attached file is documented how I checked RDO Stein Neutron OVN with
> GENEVE tunnels on ovirt-4.3.
> Please fine the steps I did only graphical in
> https://drive.google.com/file/d/16bJt3YhnlNyZzB89ozcLrHFsmpDAQqOH/
> view?usp=sharing
> 
> I deployed via packstack, but I would be happy to learn how to do this with
> TripleO.

I've deployed on  kolla containers , i've only tested the keystone Auth APIv3 from ovirt , not end to end test.

Comment 11 Evgeny Slutsky 2020-07-09 11:45:48 UTC
I can confirm neutron and keystone integration is working with OpenStack - stein (packstack default configuration - keystone v3 and neutron v2).

Comment 12 Sandro Bonazzola 2020-09-18 07:11:55 UTC
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.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.