juju 3.1 ERROR model cache:did not appear in cache timeout

ubuntu@juju:~$ juju --version 3.1.6-genericlinux-amd64

cloud: maas

After creating some models juju stops running commands

this is my situation:

ubuntu@juju:~$ juju models --uuid Controller: maas-controller

Model UUID Cloud/Region Type Status Machines Cores Units Access Last connection controller d42feb9b-6394-4d0b-8811-b481f3a824a6 maas-cloud/default maas available 1 2 2 admin just now openstack* 53068b88-f4cf-410d-8ca2-bc95a72c0004 maas-cloud/default - 0 - - - 2023-12-26 openstack-invalsi c3b46164-8689-4bed-81cd-8769c5f1bfae maas-cloud/default maas available 0 - - admin 15 hours ago openstack-invalsi2 972552fc-12c9-4dbd-867f-5a69dcb02f0e maas-cloud/default maas available 0 - - admin 14 hours ago test c91490f4-7fdf-466e-81c5-f8771250219a maas-cloud/default maas available 0 - - admin 7 minutes ago test-cloud 4b8b7ff4-d847-4c2f-8ac9-61b14c2c88a2 maas-cloud/default maas available 0 - - admin 14 hours ago test-cloud2 479f4517-6f98-4755-88f0-468f5ca5ee7d maas-cloud/default maas available 0 - - admin 14 hours ago

if I try to run a juju command with a model but controller, it returns this error: ERROR model cache: model “016713a2-46e4-49b2-8536-6c49573344dd” did not appear in cache timeout where uuid is related to the model

If I try to delete the model, even with --destroy, juju remains undefinitely working

juju debug-log works only if I switch to the controller model ubuntu@juju:~$ juju switch controller maas-controller:admin/controller (no change)

juju debug-log machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “53068b88-f4cf-410d-8ca2-bc95a72c0004” in 6.315236ms machine-0: 10:13:27 ERROR juju.worker.modelcache watcher error: error loading entities for model 53068b88-f4cf-410d-8ca2-bc95a72c0004: failed to initialise backing for models:53068b88-f4cf-410d-8ca2-bc95a72c0004: settings doc “53068b88-f4cf-410d-8ca2-bc95a72c0004:e” not found, getting new watcher machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “d42feb9b-6394-4d0b-8811-b481f3a824a6” in 15.022004ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “53068b88-f4cf-410d-8ca2-bc95a72c0004” in 5.38232ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “d42feb9b-6394-4d0b-8811-b481f3a824a6” in 14.041393ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “53068b88-f4cf-410d-8ca2-bc95a72c0004” in 5.285957ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “d42feb9b-6394-4d0b-8811-b481f3a824a6” in 13.618787ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “53068b88-f4cf-410d-8ca2-bc95a72c0004” in 5.5451ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “d42feb9b-6394-4d0b-8811-b481f3a824a6” in 14.8453ms machine-0: 10:13:27 INFO juju.state.allwatcher allwatcher loaded for model “53068b88-f4cf-410d-8ca2-bc95a72c0004” in 5.714984ms

where the uuids are related to all the controllers with errors

I got the same thing on juju 3.4.0 using terraform…