Project

General

Profile

Actions

Support #22928

closed

Upgrade Ansible to 10.x (ansible-core 2.17)

Added by Brett Smith 10 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Due date:
Story points:
-
Release relationship:
Auto

Description

After we drop support for Debian 11, all our supported distributions will have Python 3.10+. Per the ansible-core support matrix, this means we can upgrade to Ansible 10.x. This would be good to do because Ansible is pretty security-sensitive (it SSHes into all your servers with root privileges) and Ansible 8.x was already EOL when we started using it. Using a version that can get security updates is a win.

  • Test our playbooks on it
  • Deploy it to our Jenkins nodes
  • Update our documentation

Related issues 1 (0 open1 closed)

Blocked by Arvados - Support #22864: Drop support for Ubuntu 20.04 and Debian 11ResolvedBrett SmithActions
Actions #1

Updated by Brett Smith 10 months ago

  • Blocked by Support #22864: Drop support for Ubuntu 20.04 and Debian 11 added
Actions #2

Updated by Brett Smith 10 months ago

  • Description updated (diff)
Actions #3

Updated by Brett Smith 10 months ago

  • Subject changed from Upgrade Ansible to 10.x to Upgrade Ansible to 10.x (ansible-core 2.17)
Actions #4

Updated by Peter Amstutz 10 months ago

  • Target version set to Development 2025-07-09
Actions #5

Updated by Brett Smith 9 months ago

  • Target version deleted (Development 2025-07-09)
Actions #6

Updated by Brett Smith 9 months ago

  • Release set to 79
Actions #7

Updated by Brett Smith 7 months ago

  • Tracker changed from Feature to Support
Actions #8

Updated by Brett Smith 6 months ago

  • Target version set to Development 2025-10-01
  • Assigned To set to Brett Smith
  • Status changed from New to In Progress

I have tested install-dev-tools.yml and install-arvados-cluster.yml and a Workbench image build locally and they all continue to work fine. Building a new Jenkins image at packer-build-jenkins-image-arvados-tests: #142

Actions #9

Updated by Brett Smith 6 months ago

Since that passed, the easiest thing to do at this point is to merge the branch and let it run through the build pipeline. If it causes a major problem, we'll just revert.

Actions #10

Updated by Brett Smith 6 months ago

Pushed 6f550ad81a197593a72f7c15964c33c97d798a98 for the reasons discussed in the commit message. packer-build-jenkins-image-arvados-tests: #143 - now running with this.

Actions #11

Updated by Brett Smith 6 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF