-
Notifications
You must be signed in to change notification settings - Fork 13
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
Unable to deploy a bundle using model.deploy #116
Comments
agreed, this is breaking in the integration tests for this plugin itself @cderici i believe this is an issue with python-libjuju. Do you agree? |
Yeah that output looks very weird. I'm not quite sure if it's the pylibjuju client in particular, but definitely something seems to be going on on the Juju side. I'll try to reproduce this today and see what might be happening 👍 |
@addyess pylibjuju master branch tip (basically the same with 3.2.2), juju 3.1.6 on microk8s 1.27.6 python -m asyncio
asyncio REPL 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] on linux
Use "await" directly instead of "asyncio.run()".
Type "help", "copyright", "credits" or "license" for more information.
>>> import asyncio
>>> from juju import model;m=model.Model();await m.connect()
>>> await m.deploy(entity_url="https://charmhub.io/cos-lite", trust=True)
[<Application entity_id="alertmanager">, <Application entity_id="loki">, <Application entity_id="prometheus">, <Application entity_id="traefik">, <Application entity_id="catalogue">, <Application entity_id="grafana">]
>>> But as I was writing this, I just realized I saw that weird error from bundles before, and sure enough, looks like I fixed it in a run-by not so long ago in juju/python-libjuju#949, you can see a similar error message in the description. So basically this issue will go away when we make a new latest release on libjuju, which should be pretty soon 👍 |
Hello Team,
In my integration tests, I'm not able to deploy a bundle using
ops_test.model.deploy
as shown in the snippet below:The error I'm getting is:
My env is:
Workaround is of course running deployment using
ops_test.run
, but I'd rather use a proper way to deploy bundles.BR,
Bartek
The text was updated successfully, but these errors were encountered: