Bug 1566012

Summary:	Kuryr does not use Octavia API directly
Product:	Red Hat OpenStack	Reporter:	Tomas Sedovic <tsedovic>
Component:	openstack-kuryr-kubernetes	Assignee:	Antoni Segura Puimedon <asegurap>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	asegurap, jschluet, juriarte, racedoro, sclewis
Target Milestone:	beta	Keywords:	Triaged
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-kuryr-kubernetes-0.4.2-1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 13:50:58 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 Tomas Sedovic 2018-04-11 10:54:00 UTC

Description of problem:

When using Kuryr on OSP 13 (with Octavia) it should talk to the Octavia API directly, instead of using the lbaasv2 API and endpoint in Neutron.

See: https://bugzilla.redhat.com/show_bug.cgi?id=1564188

This means that creating kubernetes services (which use Octavia behind back).

Version-Release number of selected component: 0.4.1

How reproducible: Always

Steps to Reproduce:
1. Get OSP 13 with Octavia
2. Install OCP with Kuryr
3. Create a pod which results in a kubernetes service creation

Actual results:
The service will not be created because the Octavia loadbalancer creation will fail.

Expected results:
The service will be created and working properly.

Additional info:

Comment 9 Jon Uriarte 2018-04-30 16:12:47 UTC

Verified in:
openstack-kuryr-kubernetes-common-0.4.2-1.el7ost.noarch
openstack-kuryr-kubernetes-controller-0.4.2-1.el7ost.noarch

The kubernetes service is correctly created and accessed.

Comment 11 errata-xmlrpc 2018-06-27 13:50:58 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/RHEA-2018:2086