search

canonical / charmed-openstack-upgrader

Automatic upgrade tool for Charmed Openstack
Apache License 2.0
3 stars 12 forks source link

wait_for_active_idle failed #500

Closed samuelallan72 closed 2 months ago

samuelallan72 commented 2 months ago

I had a situation where the Verify that all OpenStack applications are in idle state step failed, even though all applications were in active/idle. This was running cou installed locally in a venv with pip install -e .. It was on latest main branch apart from some local changes to the nova-compute class (should be unrelated). Running cou from the latest/edge snap succeeded.

Would you like to start the upgrade? Continue (y/N): y
2024-07-18 17:07:50 [INFO] Starting the upgrade.
Running cloud upgrade...
2024-07-18 17:07:50 [INFO] Running: Upgrade cloud from 'ussuri' to 'victoria'
2024-07-18 17:07:50 [INFO] Running: Verify that all OpenStack applications are in idle state
Verify that all OpenStack applications are in idle state /2024-07-18 17:08:38 [INFO] function wait_for_active_idle failed [0]
Verify that all OpenStack applications are in idle state |/redacted/path/to/charmed-openstack-upgrader/cou/utils/juju_utils.py:106: RuntimeWarning: coroutine 'Connection.reconnect' was never awaited
  attempt += 1
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Verify that all OpenStack applications are in idle state \/redacted/path/to/charmed-openstack-upgrader/venv/lib/python3.12/site-packages/juju/utils.py:191: RuntimeWarning: coroutine 'Connection.reconnect' was never awaited
  return task.result()  # may raise exception
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2024-07-18 17:09:28 [INFO] function wait_for_active_idle failed [1]
Verify that all OpenStack applications are in idle state /2024-07-18 17:10:19 [INFO] function wait_for_active_idle failed [2]
Verify that all OpenStack applications are in idle state ✖
The connection was lost.
Check your connection or increase the timeout.
Default timeout is 10s; to increase to 60s for example:
$ COU_TIMEOUT=60 cou plan
samuelallan72 commented 2 months ago

Ah never mind, I think another error (related to my wip changes) was causing it, but for some reason that error wasn't printed the first time. :thinking: