m = Model(); await m.connect()
unknown facade CrossModelSecrets
unexpected facade CrossModelSecrets found, unable to decipher version to use
unknown facade SecretBackendsManager
unexpected facade SecretBackendsManager found, unable to decipher version to use
unknown facade SecretBackendsRotateWatcher
unexpected facade SecretBackendsRotateWatcher found, unable to decipher version to use
unknown facade SecretsRevisionWatcher
unexpected facade SecretsRevisionWatcher found, unable to decipher version to use
This version was tested using 3.1.0 juju version 3.2-beta1 may have compatibility issues
This version was tested using 3.1.0 juju version 3.2-beta1 may have compatibility issues
When using a 3.1.2 controller (latest/stable) I can operate with python-libjuju 3.1.0.1.
```
juju status
Model Controller Cloud/Region Version SLA Timestamp
toremoveme test312 microk8s/localhost 3.1.2 unsupported 11:56:45+02:00
from juju.model import Model
m = Model(); await m.connect()
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
```
As mentioned by @cderici please, check the python-libjuju version that is currently being used and the controller you're connecting go. You can see the controller version in python-libjuju using:
```
from juju.controller import Controller
c = Controller(); await c.connect()
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
I ran an additional test using 3.1.0.1 with juju 3.2-beta1 which adds unknown facades and the operability can be maintained. See below:
juju show-controller | grep agent-version
agent-version: 3.2-beta1
```
from juju.model import Model
m = Model(); await m.connect() anager anager found, unable to decipher version to use otateWatcher otateWatcher found, unable to decipher version to use Watcher Watcher found, unable to decipher version to use
unknown facade CrossModelSecrets
unexpected facade CrossModelSecrets found, unable to decipher version to use
unknown facade SecretBackendsM
unexpected facade SecretBackendsM
unknown facade SecretBackendsR
unexpected facade SecretBackendsR
unknown facade SecretsRevision
unexpected facade SecretsRevision
This version was tested using 3.1.0 juju version 3.2-beta1 may have compatibility issues
This version was tested using 3.1.0 juju version 3.2-beta1 may have compatibility issues
a = await m.deploy("ubuntu")
status = await m.get_status()
status[ 'applications' ]['ubuntu' ]['status' ] _definitions. DetailedStatus' >({'data' : {}, 'err': None, 'info': 'waiting for machine', 'kind': '', 'life': '', 'since': '2023-04- 14T09:44: 32.538357359Z' , 'status': 'waiting', 'version': '', 'unknown_fields': {}})
<class 'juju.client.
```
When using a 3.1.2 controller (latest/stable) I can operate with python-libjuju 3.1.0.1.
```
juju status
Model Controller Cloud/Region Version SLA Timestamp
toremoveme test312 microk8s/localhost 3.1.2 unsupported 11:56:45+02:00
from juju.model import Model
m = Model(); await m.connect()
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
```
As mentioned by @cderici please, check the python-libjuju version that is currently being used and the controller you're connecting go. You can see the controller version in python-libjuju using:
```
from juju.controller import Controller
c = Controller(); await c.connect()
This version was tested using 3.1.1 juju version 3.1.2 may have compatibility issues
c.connection( ).info[ "server- version" ]
```