Bug 1613922

Summary: [RFE][Glance] Ensure Glance is fully Python 3 compatible
Product: Red Hat OpenStack Reporter: Cyril Roelandt <cyril>
Component: openstack-glanceAssignee: Cyril Roelandt <cyril>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: medium Docs Contact: Kim Nylander <knylande>
Priority: medium    
Version: 15.0 (Stein)CC: aavraham, akekane, cschwede, eglynn, mabrams, pgrist, scohen, srevivo, tshefi
Target Milestone: Upstream M2Keywords: FutureFeature, TestOnly, Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-glance-18.0.1-0.20190420013840.f772321.el8ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1554014 Environment:
Last Closed: 2019-09-21 11:16:49 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:
Bug Depends On: 1554014    
Bug Blocks:    

Comment 4 Cyril Roelandt 2018-10-04 13:19:09 UTC
Let us keep in mind this workaround Erno talked about:

"Due to eventlet bug, glance-api won't be able to terminate ssl/tsl connections anymore, so if we need to have encryption on the network all the way to the node we will need to deploy stunnel or something similar in front and make glance just listening localhost".

This will require documentation.

Comment 6 Abhishek Kekane 2018-10-25 05:58:36 UTC
I have tested all glance api's with python 3 enabled using devstack setup, everything is working as expected. We just need to keep in mind about evetnlet issue and workaround mention in comment #4.

Comment 11 Cyril Roelandt 2019-06-05 13:14:11 UTC
Mike is working on this, so I believe it should already be ON_QA. Mike?

Comment 14 Cyril Roelandt 2019-07-10 18:32:44 UTC
Thanks Mike!

Comment 16 errata-xmlrpc 2019-09-21 11:16:49 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