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 setup flags to ensure connection plugins are always configured.

Bug Fixes:

  • Fix container-based integration tests by ensuring connection plugins are always installed and their environment variables are never skipped.

CI:

  • Bump tox-lsr dependency from 3.17.0 to 3.17.1 across GitHub Actions workflows.
  • Remove use of SKIP_CALLBACK_PLUGINS flag in qemu-kvm integration workflow and rely on idempotent setup instead.

…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
Copy Markdown

sourcery-ai bot commented Mar 13, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates GitHub workflows to use tox-lsr 3.17.1 (which fixes container connection plugin handling) and adjusts the qemu-kvm integration test loop so callback/connection plugin setup is never skipped, resolving broken container tests.

Sequence diagram for container test execution in CI using tox_lsr_3_17_1

sequenceDiagram
    actor Developer
    participant GitHubActions as GitHub_Actions_Workflow
    participant Runner as GHA_Runner
    participant ToxLSR as tox_lsr_3_17_1
    participant Ansible as Ansible_Tests

    Developer->>GitHubActions: Push_commit_or_open_PR
    GitHubActions->>Runner: Start_ansible_test_job

    Runner->>Runner: pip_install_tox_lsr_3_17_1
    Runner->>ToxLSR: Run_tox_with_container_env

    ToxLSR->>ToxLSR: Setup_callback_plugins_idempotent
    ToxLSR->>ToxLSR: Setup_connection_plugin_idempotent
    ToxLSR->>Runner: Set_ANSIBLE_CONNECTION_PLUGINS_env

    Runner->>Ansible: Invoke_container_tests
    Ansible->>Runner: Use_connection_plugin_from_ANSIBLE_CONNECTION_PLUGINS
    Ansible-->>GitHubActions: Report_test_results
Loading

Flow diagram for plugin setup logic before and after tox_lsr_3_17_1_fix

flowchart TD
    subgraph Before_tox_lsr_3_17_1
        B_start(["Start_container_test_env"])
        B_start --> B_check_skip["Was_plugin_setup_function_skipped?"]
        B_check_skip -->|"Yes"| B_no_conn["No_connection_plugin_installed"]
        B_no_conn --> B_no_env["ANSIBLE_CONNECTION_PLUGINS_not_set"]
        B_no_env --> B_fail["Container_tests_fail"]
        B_check_skip -->|"No"| B_setup_both["Setup_callback_and_connection_plugins"]
        B_setup_both --> B_set_env["Set_ANSIBLE_CONNECTION_PLUGINS"]
        B_set_env --> B_tests_ok["Container_tests_can_run"]
    end

    subgraph After_tox_lsr_3_17_1
        A_start(["Start_container_test_env"])
        A_start --> A_setup_callbacks["Setup_callback_plugins_idempotent"]
        A_setup_callbacks --> A_setup_conn["Setup_connection_plugin_idempotent"]
        A_setup_conn --> A_set_env["Always_set_ANSIBLE_CONNECTION_PLUGINS"]
        A_set_env --> A_tests_ok["Container_tests_always_have_connection_plugin"]
    end
Loading

File-Level Changes

Change Details Files
Update all CI workflows to use tox-lsr 3.17.1 instead of 3.17.0.
  • Bump tox-lsr dependency version from 3.17.0 to 3.17.1 in the qemu-kvm integration test workflow.
  • Bump tox-lsr dependency version from 3.17.0 to 3.17.1 in the ansible-lint workflow.
  • Bump tox-lsr dependency version from 3.17.0 to 3.17.1 in the ansible-managed-var-comment workflow.
  • Bump tox-lsr dependency version from 3.17.0 to 3.17.1 in the ansible-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
Ensure callback/connection plugin setup is always executed during qemu-kvm integration tests instead of being skipped on subsequent test runs, and fix a minor indentation issue.
  • Remove SKIP_CALLBACK_PLUGINS environment variable exports so the underlying tox-lsr logic always sets up callback and connection plugins.
  • Fix indentation of the conditional that checks for the 'containerbuild' galaxy tag in meta/main.yml to align with surrounding shell code.
.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 left some high level feedback:

  • The tox-lsr version is hard-coded in several workflow files; consider centralizing this (e.g., via a reusable workflow or shared env var) 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 several workflow files; consider centralizing this (e.g., via a reusable workflow or shared env var) 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 01ebf21 into main Mar 13, 2026
11 checks passed
@richm richm deleted the tox-lsr-3.17.1 branch March 13, 2026 16:02
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