-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ops_test.model.deploy behavior not the same as juju 3.6-beta deploy behavior with respect to chosen base of application to deploy #1090
Comments
@shayancanonical are you able to work around this issue by specifying the base to use? |
@hmlanigan yes, i had to explicitly specify the base as a workaround to continue with testing our charms with juju 3.6-beta |
…issue The test is randomly failing on libjuju 3.5.2.0 with Juju 3.6-beta2, it is a known issue reported as juju/python-libjuju#1090 As a (temporary?) workaround lets add a base here.
Hi, we have started testing juju 3.6 nightly and it affects our CI. Thank you! |
…#506) * [DPE-5480] Add base to test_multi_relations.py to workaround libjuju issue The test is randomly failing on libjuju 3.5.2.0 with Juju 3.6-beta2, it is a known issue reported as juju/python-libjuju#1090 As a (temporary?) workaround lets add a base here.
I believe this is due to a subtle change in Juju 3.6: That being said, there's also a bug in this library: #1171 |
Description
We are using
ops_test.model.deploy
in our integration tests. While testing with juju 3.4.4 (along with python-libjuju^3.2.2
) we are able to run the following code:However, while testing with juju 3.6-beta2 (along with python-libjuju
3.5.2.0
), running the above code pulls in base[email protected]/stable
sometimes and base[email protected]/stable
other times. The charm mysql-test-app is available for both focal and jammy.Example of the same code but different bases pulled:
Because (likely) juju 3.6 no longer supports certain bases (like
[email protected]/stable
), the default base python-libjuju uses inops_test.model.deploy()
fails with an error trace (shown in the reproduce section)Urgency
Annoying bug in our test suite
Python-libjuju version
3.5.2.0
Juju version
3.6-beta2-ubuntu-amd64
Reproduce / Test
Using:
We get the following trace:
Using juju 3.6-beta2 directly:
The text was updated successfully, but these errors were encountered: