Oleksandr K.
Oleksandr K.
Here are the related logs. Listener creation is failing with `Not Found: Secrets container not found` error in octavia side. As you can see the following octavia and barbican log,...
Hi @dulek did you have a chance to check the logs I provided?
@dulek did you have a chance to check?
> @okozachenko1203 > > According to your logs, the secrets were created using the internal barbican endpoint and they're requested by OCCM using a public endpoint: > > > http://barbican-api.openstack.svc.cluster.local:9311/v1/secrets/bfc96ae2-2f11-4d98-9094-8a89d0fcdcf5...
> I see, so the problem is that modern octavia requires container, not a secret? And the container is not created by the ingress controller, right? Looks related to the...
Hi folks, any update or thoughts here?
/remove-lifecycle stale
this issue has been fixed already https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2475 https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2478