Bug 1743716

Summary:	Openstack RDO Stein Keystone APIv3 Integration
Product:	[oVirt] ovirt-engine	Reporter:	Evgeny Slutsky <eslutsky>
Component:	BLL.Storage	Assignee:	Dominik Holler <dholler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	high	Docs Contact:
Priority:	high
Version:	future	CC:	aefrat, bugs, dholler, fgavrilo, mperina, pkubica, sfishbai, tnisan
Target Milestone:	ovirt-4.4.1	Flags:	sbonazzo: ovirt-4.4? sbonazzo: planning_ack? pm-rhel: devel_ack+ pm-rhel: testing_ack+
Target Release:	4.4.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.1.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-05 06:25:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Evgeny Slutsky 2019-08-20 14:11:58 UTC

since openstack Stein  Identity API v2 is deprecated (https://docs.openstack.org/keystone/stein/contributor/http-api.html)
engine support only keystone API version 2.

Keyston API affects those External  Openstack providers:
- Glance for Image Management.
- Neutron Network Provisioning
- Cinder for Storage Management

Comment 1 Sandro Bonazzola 2019-08-22 11:58:34 UTC

Raising severity and urgency, limiting to high just because Pike is still maintained according to https://releases.openstack.org/.

Comment 5 Tal Nisan 2020-06-29 12:16:26 UTC

Needinfo should be moved to Dominik who fixed the issue

Comment 7 Sandro Bonazzola 2020-07-02 11:59:23 UTC

$ git tag --contains f8ce33587cff4e64c04c78e89ecb01210ac1f8d8
ovirt-engine-4.4.1.3
ovirt-engine-4.4.1.4
ovirt-engine-4.4.1.5

Comment 9 Petr Kubica 2020-07-09 11:44:31 UTC

Verified with openstack-train
Authentication with keystone works

Comment 10 Sandro Bonazzola 2020-08-05 06:25:36 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

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