Skip to content

ci: tox-lsr 3.17.1 - previous update broke container tests, this fixes them [citest_skip]#134

Merged
richm merged 1 commit intomainfrom
tox-lsr-3.17.1
Mar 13, 2026
Merged

ci: tox-lsr 3.17.1 - previous update broke container tests, this fixes them [citest_skip]#134
richm merged 1 commit intomainfrom
tox-lsr-3.17.1

Conversation

@richm
Copy link
Copy Markdown
Contributor

@richm richm commented Mar 13, 2026

tox-lsr 3.17.1 has a fix for the broken container tests

There was one shell function for both setting up the callback plugins and the connection plugin.
When this function was skipped, the ANSIBLE_CONNECTION_PLUGINS environment variable was not
set, so all subsequent tests failed. The connection plugin must be present and the env. var.
must be set in order to run any container tests. The code was fixed to ensure that there is
always a connection plugin installed in the correct location and that ANSIBLE_CONNECTION_PLUGINS
is always set and contains this path.

Also, setting up the callback plugins and the connection plugin is already idempotent, so no
reason to skip them.

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

Summary by Sourcery

Update CI workflows to use tox-lsr 3.17.1 and adjust container test configuration to ensure connection plugins are always set up.

Bug Fixes:

  • Ensure container integration tests always configure required Ansible connection plugins by no longer skipping their setup between test runs.

CI:

  • Bump tox-lsr dependency from 3.17.0 to 3.17.1 across GitHub Actions workflows.
  • Fix indentation and SKIP_* environment handling in qemu-kvm integration workflow to align with updated tox-lsr behavior.

…s them [citest_skip]

tox-lsr 3.17.1 has a fix for the broken container tests

There was one shell function for both setting up the callback plugins and the connection plugin.
When this function was skipped, the ANSIBLE_CONNECTION_PLUGINS environment variable was not
set, so all subsequent tests failed.  The connection plugin must be present and the env. var.
must be set in order to run any container tests.  The code was fixed to ensure that there is
always a connection plugin installed in the correct location and that ANSIBLE_CONNECTION_PLUGINS
is always set and contains this path.

Also, setting up the callback plugins and the connection plugin is already idempotent, so no
reason to skip them.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
@richm richm requested a review from spetrosi as a code owner March 13, 2026 15:27
@richm richm self-assigned this Mar 13, 2026
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Mar 13, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates GitHub Actions workflows to use tox-lsr 3.17.1 and adjusts qemu-kvm integration-test logic so callback/connection plugins are always configured, fixing broken container tests and correcting a minor shell indentation issue.

Sequence diagram for qemu_kvm container tests ensuring connection plugin setup

sequenceDiagram
  participant GH as GitHubActionsRunner
  participant WF as qemu_kvm_workflow
  participant Tox as tox
  participant ToxLSR as tox_lsr_3_17_1
  participant Ansible as ansible_core
  participant Conn as connection_plugin

  GH->>WF: Trigger workflow on push or PR
  WF->>Tox: Run tox environment for qemu_kvm tests
  Tox->>ToxLSR: Load linux_system_roles tox configuration
  ToxLSR->>ToxLSR: Ensure callback plugins directory exists
  ToxLSR->>ToxLSR: Ensure connection plugin installed in correct path
  ToxLSR->>ToxLSR: Set ANSIBLE_CONNECTION_PLUGINS to include plugin path
  ToxLSR->>Ansible: Invoke ansible tests for containers
  Ansible->>Conn: Use configured connection plugin for container access
  Ansible-->>WF: Report test results
  WF-->>GH: Publish qemu_kvm container test status
Loading

Flow diagram for idempotent plugin setup without skipping

flowchart TD
  A[start qemu_kvm container test job] --> B[install tox_lsr_3_17_1]
  B --> C[run tox environment]
  C --> D[run setup_plugins function]

  subgraph setup_plugins
    D --> E[ensure callback plugins directory exists]
    E --> F[ensure connection plugin file is present]
    F --> G[export ANSIBLE_CONNECTION_PLUGINS including plugin path]
  end

  G --> H[run ansible container tests]
  H --> I{tests complete?}
  I -->|yes| J[end job]
  I -->|no, retry or fail| K[report failure]
  K --> J

  classDef changed fill:#fffbdd,stroke:#d2a106,stroke-width:1px
  class B,C,D,E,F,G changed
Loading

File-Level Changes

Change Details Files
Update CI to use tox-lsr 3.17.1, which fixes container test setup for connection plugins.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in qemu-kvm integration test workflow.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in ansible-lint workflow.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in ansible-managed-var-comment workflow.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in ansible-test workflow.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in python-unit-test workflow.
.github/workflows/qemu-kvm-integration-tests.yml
.github/workflows/ansible-lint.yml
.github/workflows/ansible-managed-var-comment.yml
.github/workflows/ansible-test.yml
.github/workflows/python-unit-test.yml
Adjust qemu-kvm integration test loop so callback/connection plugin setup is never skipped and fix indentation in container tag check.
  • Remove SKIP_CALLBACK_PLUGINS environment variable toggling so callback/connection plugins are always configured for each test run.
  • Fix indentation for the yq containerbuild tag check to match the surrounding shell if-block style.
.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

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@richm richm merged commit 6ea6da5 into main Mar 13, 2026
14 checks passed
@richm richm deleted the tox-lsr-3.17.1 branch March 13, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant