Bug 1799313

Summary:	OpenstackSDK not used in whole kuryr-kubernets project.
Product:	OpenShift Container Platform	Reporter:	rdobosz
Component:	Networking	Assignee:	rdobosz
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	itbrown, mdulko
Version:	4.4	Flags:	gcheresh: needinfo+
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 21:56:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description rdobosz 2020-02-06 16:32:02 UTC

Description of problem:
Recently there was a switching from neutron client to the openstacksdk client, although not all components were successfully converted.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
All of the components switched to openstacksdk, or at least drivers which are currently not possible to move, isolate within the modules.

Additional info:

Comment 1 Michał Dulko 2020-02-06 16:34:42 UTC

Worth to say that it may lead to undefined behaviors - e.g. some code doesn't handle exceptions from python-neutronclient anymore.

Comment 3 GenadiC 2020-03-03 13:07:26 UTC

Please provide steps to reproduce this - it's too general

Comment 4 GenadiC 2020-03-03 13:07:50 UTC

Please provide steps to reproduce this - it's too general

Comment 5 rdobosz 2020-03-03 13:33:30 UTC

From user perspective, it's kind of undistinguishable from previous implementation - it is rather an improvement for code maintenance and being able to keep up with changes to the API/clients in one place.

What is affected by this change:

- handlers:
  - namespace
  - kuryrnet
  - vif
  - lbaas

- drivers:
  - all but macvlan nested driver

Comment 6 rdobosz 2020-03-05 12:21:17 UTC

Effectively, for confirmation it's enough to run tempest tests against those patches.

Comment 7 Itzik Brown 2020-04-05 11:30:14 UTC

Verified with the following:
4.4.0-0.nightly-2020-04-04-025830

Comment 9 errata-xmlrpc 2020-05-13 21:56:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2020:0581