You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is (most likely) caused by a not ideal Ceilometer -> Panko API transition. The validation tries connect to the Panko (and Ceilometer as a fallback) service by the endpoint from Keystone catalog, not requesting actual events on the /v2/events path. This worked well until OpenStack telemetry modified Ceilometer API removing events-related functionality, but keeping other parts (port 8777 belongs to the OpenStack Ceilometer API).
Possible solutions which I can see:
update validation method with calling list_events after on the service connection [1]
if the OpenStack version is known, that has Panko (probably all currently supported versions), is it possible set config option [2] to "panko" to disable fallback to Ceilometer API, so validation will fail if there is no Panko service
Event the first solution seems better to me, stopping support Ceilometer API for Events could be more reasonable (removing the Ceilometer API fallback). I'd be suprised if some real world deployment is using Ceilometer (no Panko) events and upgrading MIQ code (however AMQP events are older, it is widely used, but the Ceilometer events was RH-like OpenStack solution and it has been replaced with Panko a time ago)
I added an Openstack provider using Ceilometer for events, the event catcher later failed on 404 for
/v2/events
But the credential validation was successful, there was no indication on the UI anywhere that event collection would fail
The text was updated successfully, but these errors were encountered: