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

Bug 1620052

Summary:	[RFE] [Kuryr] Python3 support for Stein/RHEL8
Product:	OpenShift Container Platform	Reporter:	Daniel Mellado <dmellado>
Component:	Networking	Assignee:	Michał Dulko <mdulko>
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	aos-bugs, asegurap, ltomasbo, mdulko, racedoro, tsedovic
Version:	4.2.0	Keywords:	FutureFeature, Triaged
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-kuryr-kubernetes-1.1.0-0.20190613110404.6db30e5.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:18:39 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 Daniel Mellado 2018-08-22 10:15:20 UTC

As migrating to python3 is both a goal for Stein cycle and a need for RHOS8, I'll be using this card to track the ongoing work and bugzillas related to it.

The upstream community has started the process of bootstrapping CI jobs to use python3, see below.

Process on modifying the jobs  *NOT TO BE DONE BY US*

  - http://git.openstack.org/cgit/openstack/goal-tools/tree/README.rst#n22


Weekly emails related to the py3 goal. I asked Kuryr to be addressed as an early adopter, will post back as soon as we've incoming reviews for this.

  - http://lists.openstack.org/pipermail/openstack-dev/2018-August/133232.html
  - http://lists.openstack.org/pipermail/openstack-dev/2018-August/133525.html

Comment 3 Daniel Mellado 2018-12-21 16:12:19 UTC

https://blueprints.launchpad.net/kuryr-kubernetes/+spec/goal-python36

Comment 9 errata-xmlrpc 2019-09-21 11:18:39 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-2019:2811