In order to use an updated version of python-bugzilla to be prepared for the upcoming Bugzilla authentication changes [1], I've updated review-stats dockerfile to use Fedora 35 as base image [2] in staging, but I hit https://bugzilla.redhat.com/show_bug.cgi?id=1988199
review-stats
Cloning "https://pagure.io/Fedora-Infra/review_stats.git " ... Commit: 1c61b25750ef17e50482706e14c578d6bd73d2a6 (Update Dockerfile to Fedora 35) Author: Mattia Verga <mattia.verga@tiscali.it> Date: Tue Feb 1 17:56:31 2022 +0100 Pulling image fedora:35 ... Pulled 1/2 layers, 50% complete Step 1/7 : FROM fedora:35 ---> b78af7a83692 Step 2/7 : LABEL maintainer "Clément Verna <cverna@tutatnota.com>" ---> Running in 368c844aadd9 ---> fe6cf4e49819 Removing intermediate container 368c844aadd9 Step 3/7 : RUN dnf install -y python3-click python3-bugzilla python3-jinja2 git python3-pip python3-systemd && dnf clean all ---> Running in 5dfc65e6e789 Fedora 35 - x86_64 0.0 B/s | 0 B 00:00 Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start] Removing intermediate container 5dfc65e6e789 error: build error: The command '/bin/sh -c dnf install -y python3-click python3-bugzilla python3-jinja2 git python3-pip python3-systemd && dnf clean all' returned a non-zero code: 1
I assume this is because OS cluster is still running on RHEL7? Is there any plan to switch to RHEL8 to fix that docker/podman bug or to push the fix on OS?
I've downgraded review-stats Dockerfile to F34, which have the updated python-bugzilla to avoid problems with the upcoming changes, so there's no need to hurry. Yet, it would be nice to start planning a solution for this, because it will likely impact all other openshift apps which may want to use Fedora >= 35 as base image.
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/U3PQNCLKA3R6GA2UI2EZP2OT4VAKVHBI/ [2] https://pagure.io/fedora-infra/review_stats/c/1c61b25750ef17e50482706e14c578d6bd73d2a6?branch=stg
The plan here is to migrate things to the new ocp4 cluster. 3.11 doesn't support rhel8 that I know of, and even if it did we don't want to go to all that trouble. ;(
We are adding some more compute nodes to ocp4 this week, then we should be able to start migrating things next week...
Metadata Update from @kevin: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)