Bug 2097246 - Kuryr: verify and unit jobs failing due to upstream OpenStack dropping py36 support
Summary: Kuryr: verify and unit jobs failing due to upstream OpenStack dropping py36 s...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Michał Dulko
QA Contact: Jon Uriarte
Depends On:
Blocks: 2097277
TreeView+ depends on / blocked
Reported: 2022-06-15 09:43 UTC by Michał Dulko
Modified: 2022-08-10 11:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:17:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 672 0 None open Bug 2097246: Use upper-constraints.txt from stable/xena in UT 2022-06-15 09:45:07 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:18:10 UTC

Description Michał Dulko 2022-06-15 09:43:59 UTC
Description of problem:
In OpenShift we only have Python 3.6. OpenStack recently dropped compatibility with it, dropping the 3.6 compatible versions from requirements. This means that until we switch back to a 3.6-compat requirements, our verify and unit jobs will be broken.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Check current CI results.

Actual results:

Expected results:

Additional info:
This doesn't need verification other than PR passing the CI.

Comment 1 Michał Dulko 2022-06-15 10:17:28 UTC
I'm moving directly to VERIFIED, the CI passed on the PR and that was the point.

Comment 3 errata-xmlrpc 2022-08-10 11:17:59 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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