Bug 1623892
| Summary: | Neutron python 3.6 support | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Bernard Cafarelli <bcafarel> | |
| Component: | openstack-neutron | Assignee: | Nate Johnston <njohnston> | |
| Status: | CLOSED ERRATA | QA Contact: | Candido Campos <ccamposr> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 15.0 (Stein) | CC: | amuller, chrisw, ekuris, skaplons, srevivo, tfreger | |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, Triaged | |
| Target Release: | 15.0 (Stein) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-neutron-14.0.2-0.20190607050454.7b0b4ed.el8ost | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1708785 (view as bug list) | Environment: | ||
| Last Closed: | 2019-09-21 11:18:46 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: | ||||
| Bug Blocks: | 1708785 | |||
|
Description
Bernard Cafarelli
2018-08-30 11:49:57 UTC
Neutron support for python 3.6 support is currently underway upstream. Main items are: - debug functional tests; there is improper usage somewhere in the Neutron functional test harness - determine how to switch upstream grenade/tempest jobs from 2.7 to 3.6 Will track any additional upstream items here. Switch of U/S CI jobs to python3 is tracked in https://etherpad.openstack.org/p/neutron_ci_python3 Only grenade jobs upstream are not python3 (will be soon), apart from that upstream python3 support is good I believe the effort to support python 3.6 upstream is concluded successfully. 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 |