Python-312-minimal container is failing on 'test-openshift-4'

[phracek]

The test test_python_s2i_app_ex is failing.

The reason is:

oc logs pod/python-312-minimal-testing-1-build
Defaulted container "sti-build" out of: sti-build, git-clone (init), manage-dockerfile (init)
time="2025-02-04T11:38:51Z" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
I0204 11:38:51.418497       1 defaults.go:112] Defaulting to storage driver "overlay" with options [mountopt=metacopy=on].
Caching blobs under "/var/cache/blobs".
Trying to pull image-registry.openshift-image-registry.svc:5000/sclorg-test-16868/python-312-minimal@sha256:75c72aa83a345f42c8b5e12afce0928537e26d2424a5dfd2c612771a8f8b2bce...
Getting image source signatures
Copying blob sha256:1df64e3ca5fd3def3eaa8e25737b009a6249ccb12e6b32318702efc506749423
Copying blob sha256:7773c651ce2558c22521f6ea1bb2e11b3a7e0f291de522fb1183c6ab4e62c1a6
Copying blob sha256:7c9d284b2661fdfadc543496653779398b0a336d10713468ba7dc849af124378
Copying blob sha256:24436b52f270faaf1cd45508746ed85af4420ecadbf33becda289f2e4221eb18
Copying blob sha256:f7b6c76e1417077c7d494328f6e92dbdf8149653a602d4e64c42030f89919a3d
Copying blob sha256:baf71d57574699203d8cac99d31560360791d85ea4d094540ffca5d4ea6833b3
Copying blob sha256:0ed5ae7f2b5542e33f8e2e908ce5bf4b2442945f8ad51f755f2ec4247351b719
Copying config sha256:d5907ed32391fc6f1db2f5581733647230bc973c02a549ff3cb752de3c1b152e
Writing manifest to image destination
Generating dockerfile with builder image image-registry.openshift-image-registry.svc:5000/sclorg-test-16868/python-312-minimal@sha256:75c72aa83a345f42c8b5e12afce0928537e26d2424a5dfd2c612771a8f8b2bce
Adding transient rw bind mount for /run/secrets/rhsm
STEP 1/9: FROM image-registry.openshift-image-registry.svc:5000/sclorg-test-16868/python-312-minimal@sha256:75c72aa83a345f42c8b5e12afce0928537e26d2424a5dfd2c612771a8f8b2bce
STEP 2/9: LABEL "io.openshift.build.image"="image-registry.openshift-image-registry.svc:5000/sclorg-test-16868/python-312-minimal@sha256:75c72aa83a345f42c8b5e12afce0928537e26d2424a5dfd2c612771a8f8b2bce"       "io.openshift.build.commit.author"="Petr Hracek <phracek@redhat.com>"       "io.openshift.build.commit.date"="Wed Jun 5 15:09:22 2024 +0200"       "io.openshift.build.commit.id"="587173e8ddfbf060a2ecd9cb636504b57c5dad66"       "io.openshift.build.commit.ref"="2.2.x"       "io.openshift.build.commit.message"="Update django.json"       "io.openshift.build.source-location"="https://github.com/sclorg/django-ex.git"
STEP 3/9: ENV OPENSHIFT_BUILD_NAME="python-312-minimal-testing-1"     OPENSHIFT_BUILD_NAMESPACE="sclorg-test-16868"     OPENSHIFT_BUILD_SOURCE="https://github.com/sclorg/django-ex.git"     OPENSHIFT_BUILD_REFERENCE="2.2.x"     OPENSHIFT_BUILD_COMMIT="587173e8ddfbf060a2ecd9cb636504b57c5dad66"
STEP 4/9: USER root
STEP 5/9: COPY upload/src /tmp/src
STEP 6/9: RUN chown -R 1001:0 /tmp/src
STEP 7/9: USER 1001
STEP 8/9: RUN /usr/libexec/s2i/assemble
---> Installing application source ...
---> Installing dependencies ...
Collecting Django<3.0,>=2.2.12 (from -r requirements.txt (line 1))
  Downloading Django-2.2.28-py3-none-any.whl.metadata (3.6 kB)
Collecting django-debug-toolbar==2.2 (from -r requirements.txt (line 2))
  Downloading django_debug_toolbar-2.2-py3-none-any.whl.metadata (3.0 kB)
Collecting gunicorn==20.0.4 (from -r requirements.txt (line 3))
  Downloading gunicorn-20.0.4-py2.py3-none-any.whl.metadata (3.5 kB)
Collecting psycopg2-binary==2.9.5 (from -r requirements.txt (line 4))
  Downloading psycopg2-binary-2.9.5.tar.gz (384 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [21 lines of output]
      running egg_info
      writing psycopg2_binary.egg-info/PKG-INFO
      writing dependency_links to psycopg2_binary.egg-info/dependency_links.txt
      writing top-level names to psycopg2_binary.egg-info/top_level.txt

      Error: pg_config executable not found.

      pg_config is required to build psycopg2 from source.  Please add the directory
      containing pg_config to the $PATH or specify the full executable path with the
      option:

          python setup.py build_ext --pg-config /path/to/pg_config build ...

      or with the pg_config option in 'setup.cfg'.

      If you prefer to avoid building psycopg2 from source, please install the PyPI
      'psycopg2-binary' package instead.

      For further information please check the 'doc/src/install.rst' file (also at
      <https://www.psycopg.org/docs/install.html>).

      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.

[notice] A new release of pip is available: 24.2 -> 25.0
[notice] To update, run: pip install --upgrade pip
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
error: build error: building at STEP "RUN /usr/libexec/s2i/assemble": while running runtime: exit status 1

[phracek]

@fila43 @frenzymadness Do you know about this error? Our NightlyBuilds tests failed.
Can you please take a look at this.

I hope it is easy to fix it.
The affected version is only python-312-minimal on RHEL8 and RHEL9

[frenzymadness]

It seems the test uses the django-ex project with version 2 which is too old and contains also an old version of psycopg2-binary. We have to switch the test to run with the newest branch of django-ex 4.2.x. The newest branch has the newest psycopg2-binary there and that version provides wheels for Python 3.12+.

[frenzymadness]

I'm reopening this because it seems that the nightly builds for ubi 8 and 9 and Python 3.12 still use Django-ex branch 2.2.x and therefore the tests are failing for the same reason as before.

@phracek do you know where to change the branch to fix it?

I see the branch hardcoded in:

• s2i-python-container/test/test_python_ex_template.py

  Line 18 in d7906ff

  BRANCH_TO_TEST = "2.2.x"

  and

• s2i-python-container/test/test_deploy_templates.py

  Line 19 in d7906ff

  BRANCH_TO_TEST = "2.2.x"

The latter already has a condition for newer Pythons so we should probably override the branch of django-ex there as well. What do you think?