Skip to content

feat: [backport 1.34] migrate integration tests to jubilant - #971

Draft
HomayoonAlimohammadi wants to merge 2 commits into
release-1.34from
KU-6190/1.34-jubilant-migration
Draft

feat: [backport 1.34] migrate integration tests to jubilant#971
HomayoonAlimohammadi wants to merge 2 commits into
release-1.34from
KU-6190/1.34-jubilant-migration

Conversation

@HomayoonAlimohammadi

Copy link
Copy Markdown
Contributor

This PR migrates e2e tests from pytest-operator to Jubilant

Backport of the pytest-operator + python-libjuju (async) to Jubilant +
pytest-jubilant (sync) integration-test migration onto release-1.34.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Homayoon (Hue) Alimohammadi <homayoon.alimohammadi@canonical.com>
@HomayoonAlimohammadi HomayoonAlimohammadi changed the title feat: migrate integration tests to jubilant feat: [backport 1.34] migrate integration tests to jubilant Jul 24, 2026
test_upgrade deployed 1.32/beta and refreshed to the locally built charm,
but release-1.34 declares upgrade_supported "^1.33, < 1.35", so the
control-plane leader failed the version check and stayed blocked:

  VersionError: Versions incompatible, k8s_service 1.32.0 can not be
  upgraded to 1.34.0

The stale default went unnoticed because charm_channel_missing() shelled
out to `juju info` at import time and the test-collection job has no juju
CLI, so the module errored out of the matrix. The jubilant migration
guards that call with shutil.which(), which put test_upgrade back in the
matrix and surfaced the failure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@HomayoonAlimohammadi
HomayoonAlimohammadi force-pushed the KU-6190/1.34-jubilant-migration branch from 6bf4f61 to aaf3bde Compare August 12, 2026 13:07
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