#1598 [spike] : investigating needed deps (poetry) for duffy on el9
Closed: Fixed 4 days ago by nphilipp. Opened 4 months ago by arrfab.

Based on a discussion with @nphilipp , we'd need to ensure that current duffy code can be easily deployed with deps on el9, as it also need to integrate easily with ansible-runner for duffy-tasks (provisioning/deprovisioning ec2 machines through ansible behind the scene)


Metadata Update from @arrfab:
- Issue assigned to nphilipp
- Issue marked as blocking: #1527
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: centos-ci-infra, dc-move, high-gain, investigation, medium-trouble

4 months ago

@nphilipp : just having a look at tickets assigned to people on centos-infra tracker and wondering if you already had a change to look at this ? Maybe worth checking with @gwmngilfen so that we can slowly plan migrating to el9 on aws ? (for ticket #1527 )

I’ve just checked this using the Centos Stream 9 image on quay.io and it seems to work well with Python versions 3.9 (system), 3.11 and 3.12 (both CRB). Here are the additional packages I installed in the base CS9 image to get it to work:

  • python3-devel, python3.11-devel, python3.12-devel, gcc, libpq-devel: to build native Python extensions
  • postgresql-server: to run tests against a private PostgreSQL instance

I ran the tests on Python 3.9 in a virtual environment:

$ python -m venv venv
$ . venv/bin/activate
(venv) $ poetry install --all-extras
(venv) $ pip install pytest-xdist
(venv) $ pytest -n auto

As a side effect, this installs tox with which to run tests with all three Python versions:

(venv) $ tox
...

As far as I judge it, this works.

Metadata Update from @nphilipp:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 days ago

Log in to comment on this ticket.