About the gnocchi in error state, that shouldn’t be due to missing relations, to get a better understanding of what’s broken there you can run juju debug-log -i gnocchi/N --replay (replacing N with the actual unit number), that should give you (hopefully) a stacktrace and some error logs to get insights of where/when the hook threw an error.
Hello guys,
Thank you for help me. The gnocchi/0 unit is now active and operational following a previous fix, but ceilometer/0 remains blocked and requires the ceilometer-upgrade action. Attempting to run this action fails with a Keystone unavailable error, even though the relation to Keystone exists.
Status of ceilometer:
ceilometer 21.0.0 blocked 1 ceilometer 2023.2/stable 552 no Run the ceilometer-upgrade action on the leader to initialize ceilometer and gnocchi
Upgrade gives me this error:
2025-09-13 09:57:36.194 242209 CRITICAL ceilometer [-] Unhandled error: gnocchiclient.exceptions.ClientException: {"message": "The server is currently unavailable. Please try again at a later time.<br /><br />\nThe Keystone service is temporarily unavailable.\n\n", "code": "503 Service Unavailable", "title": "Service Unavailable"} (HTTP 503)
what’s the status of gnocchi?, not just at the juju level, but at the payload level. You should be able to curl the service or run something like gnocchi metric list.
Also check gnocchi’s log to understand what’s the backend error that produced this 503.
