Bump ansible to v2.17.14

[mboersma]

Change description

Updates ansible-core to v2.17.14, supporting Python 3.10-3.12.

Related issues

See #1925 for prior art.

Additional context

See also #1894. I think we can get there, but maybe in baby steps...

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jsturtevant for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mboersma]

/hold

I'm not sure if we should merge this or #1972. It appears that 2.16 is more of an "LTS" release, as it's still getting patch releases while 2.17 hasn't recently.

[mboersma]

/test pull-azure-sigs
/test pull-ova-all
/test pull-gcp-all

[mboersma]

/test pull-lint

[k8s-ci-robot]

@mboersma: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-lint	16cea1e	link	true	/test pull-lint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[mboersma]

/close

Let's merge #1972, do another release (so Python 3.10 users have a known-working image-builder version), then work on fixing the linter failures in #1974.

[k8s-ci-robot]

@mboersma: Closed this PR.

Details

In response to this:

/close

Let's merge #1972, do another release (so Python 3.10 users have a known-working image-builder version), then work on fixing the linter failures in #1974.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.