Bug 1566012 – Kuryr does not use Octavia API directly

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1566012 - Kuryr does not use Octavia API directly

Summary:	Kuryr does not use Octavia API directly

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-kuryr-kubernetes (Show other bugs)
Sub Component:
Version:	13.0 (Queens)
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	beta
Target Release:	13.0 (Queens)
Assigned To:	Antoni Segura Puimedon
QA Contact:	Ofer Blaut
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-11 06:54 EDT by Tomas Sedovic
Modified:	2018-06-27 09:51 EDT (History)
CC List:	5 users (show)

See Also:
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 09:50:58 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1763045	None	None	None	2018-04-11 11:54 EDT
OpenStack gerrit	560433	None	master: MERGED	kuryr-kubernetes: lbaasv2: Fix for deployments missing the proxy (Iafd74f23bdf336a4d78ba4759f702cf989c8bc30)	2018-04-24 12:57 EDT
OpenStack gerrit	561974	None	stable/queens: MERGED	kuryr-kubernetes: lbaasv2: Fix for deployments missing the proxy (Iafd74f23bdf336a4d78ba4759f702cf989c8bc30)	2018-04-24 12:57 EDT
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:51 EDT

Groups: None (edit)

Description Tomas Sedovic 2018-04-11 06:54:00 EDT

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 12:12:47 EDT

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 09:50:58 EDT

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

Note You need to log in before you can comment on or make changes to this bug.