Skip to content

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

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]#244
richm merged 1 commit intomainfrom
tox-lsr-3.17.1

Conversation

@richm
Copy link
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 test environment flags to restore container test execution.

Build:

  • Bump tox-lsr dependency from 3.17.0 to 3.17.1 across GitHub Actions workflows.
  • Remove SKIP_CALLBACK_PLUGINS environment variable toggling in qemu-kvm integration tests to ensure required plugins and env vars are always set.

CI:

  • Fix indentation in qemu-kvm integration tests workflow condition for container build tag detection.

…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 self-assigned this Mar 13, 2026
@sourcery-ai
Copy link

sourcery-ai bot commented Mar 13, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates CI workflows to use tox-lsr 3.17.1 (which fixes broken container tests) and stops skipping callback/connection plugin setup between test runs so the required Ansible connection plugin environment is always present.

Sequence diagram for CI job ensuring Ansible connection plugin is available with tox_lsr_3_17_1

sequenceDiagram
  participant Workflow as GithubActionsWorkflow
  participant Runner as CIJobRunner
  participant Pip as PipInstaller
  participant Tox as Tox
  participant ToxLsr as ToxLsr_3_17_1
  participant Ansible as Ansible
  participant FS as Filesystem
  participant Env as Environment
  participant CTests as ContainerTests

  Workflow->>Runner: Trigger job (push or PR)
  Runner->>Pip: pip3 install git+https://github.com/linux_system_roles/tox_lsr@3.17.1
  Pip-->>Runner: tox_lsr 3.17.1 installed

  Runner->>Tox: tox run container test environment
  Tox->>ToxLsr: Initialize test environment
  ToxLsr->>FS: Install connection plugin in known path
  ToxLsr->>FS: Install callback plugins (idempotent)
  ToxLsr->>Env: Set ANSIBLE_CONNECTION_PLUGINS to connection plugin path
  ToxLsr-->>Tox: Environment prepared
  Tox->>Ansible: Execute container based test playbooks
  Ansible->>CTests: Run tests using connection plugin
  CTests-->>Ansible: Test results
  Ansible-->>Tox: Test success or failure
  Tox-->>Runner: Exit code and logs
  Runner-->>Workflow: Job status
Loading

File-Level Changes

Change Details Files
Update all GitHub Actions workflows to use tox-lsr 3.17.1 so container tests run with the fixed plugin handling.
  • Bump tox-lsr version from 3.17.0 to 3.17.1 in qemu-kvm integration, ansible-lint, ansible-managed-var-comment, ansible-test, and python-unit-test workflows.
  • Ensure all CI jobs consistently install tox-lsr from the same updated git tag.
.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
Ensure container test runs always configure callback and connection plugins instead of skipping them on subsequent test files.
  • Remove use of SKIP_CALLBACK_PLUGINS for the first and subsequent tox test runs in the qemu-kvm integration workflow so plugin setup always executes.
  • Rely on tox-lsr’s idempotent setup logic to avoid redundant work while guaranteeing ANSIBLE_CONNECTION_PLUGINS is always set.
.github/workflows/qemu-kvm-integration-tests.yml
Minor shell indentation fix in container support detection logic.
  • Fix indentation of the yq-based containerbuild tag check to keep it inside the conditional branch for differing images.
.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

@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 left some high level feedback:

  • The tox-lsr version is hard-coded in multiple workflows; consider centralizing this (e.g., via a shared action, reusable workflow, or environment variable) so future version bumps only require a single change.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The tox-lsr version is hard-coded in multiple workflows; consider centralizing this (e.g., via a shared action, reusable workflow, or environment variable) so future version bumps only require a single change.

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 7721441 into main Mar 13, 2026
14 checks passed
@richm richm deleted the tox-lsr-3.17.1 branch March 13, 2026 16:03
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