Hi there, 404 usually implies there is a mis-configuration somewhere such that a resource is not found. The dashboard uses the barbican client code to access barbican. That code is located here and pretty simple: https://github.com/openstack/octavia-...

Without more information and logs it's hard to pinpoint the issue exactly, but here are some things to investigate: 1. Check that "key-manager" is listed with the correct URL in the keystone endpoints configuration. "openstack endpoint list | grep key-manager". If that URL is incorrect It could cause the barbican client to return a 404. 2. Make sure the project you are using in the dashboard has access to barbican and that project has certificate containers and secrets. Sometimes folks will create these with a different project by accident.

Michael

Hi there, we experienced the same issue but after some investigations we found that there was a problem related to the authentication mechanism from horizon components to keystone: the authentication made a fallback from v3 to v2 causing a silent error to the request of the barbican resource.

From this code: https://github.com/openstack/octaviadashboard/blob/master/octavia_dashboard/api/rest/barbican.py (https://github.com/openstack/octaviad...)

I saw that every authentication went to v3, so I checked it in horizon and fix the api call with the correct value.

Francesco