ci: tox-lsr version 3.15.0 [citest_skip]

[richm]

This adds back support for IPv6 in qemu VMs, which appears to be working now.

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Build:

• Bump tox-lsr dependency to 3.15.0 in all GitHub Actions workflows, including qemu KVM integration tests.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the tox-lsr dependency to version 3.15.0 across all relevant GitHub Actions workflows, aligning CI and qemu-based integration tests with the newer tooling that restores IPv6 support in qemu VMs.

Flow diagram for GitHub Actions job installing tox_lsr_3_15_0

flowchart TD
  A[Workflow_triggered_by_push_or_PR] --> B[Checkout_repository]
  B --> C[Set_up_Python_environment]
  C --> D[Run_pip3_install_git_https_github_com_linux_system_roles_tox_lsr_3_15_0]
  D --> E[Run_tox_based_tasks]
  E --> F[For_qemu_kvm_integration_tests_run_tests_in_qemu_VMs_with_IPv6_support]
  E --> G[For_ansible_lint_and_plugin_scan_run_static_analysis]
  F --> H[Report_test_results]
  G --> H[Report_test_results]
  H --> I[Complete_workflow_status_pass_fail]

Loading

File-Level Changes

Change	Details	Files
Update GitHub Actions CI workflows to use tox-lsr 3.15.0 instead of 3.14.0.	Change the pip3 install command to reference tox-lsr version 3.15.0 in the ansible-lint workflow. Change the pip3 install command to reference tox-lsr version 3.15.0 in the ansible-managed-var-comment workflow. Change the pip3 install command to reference tox-lsr version 3.15.0 in the ansible-test workflow. Change the pip3 install command to reference tox-lsr version 3.15.0 in the qemu-kvm-integration-tests workflow, ensuring integration tests use the updated tox-lsr with IPv6 support for qemu VMs.	.github/workflows/ansible-lint.yml .github/workflows/ansible-managed-var-comment.yml .github/workflows/ansible-test.yml .github/workflows/qemu-kvm-integration-tests.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since the tox-lsr version is repeated across multiple workflows, consider centralizing it via a reusable workflow, composite action, or a single configuration variable to reduce the chance of inconsistent future updates.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since the tox-lsr version is repeated across multiple workflows, consider centralizing it via a reusable workflow, composite action, or a single configuration variable to reduce the chance of inconsistent future updates.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}