We have a Portal cluster enrolled and due to sync issues we tried re enrolling, after re enroll the applications got synced, however apis are not syncing. I tried re enrolling a few times but the behavior is the same.
Can you please guide us on this.
Portal version -> 5.1.2.1
Release : 5.1.2
Data container was unable to connect to RabbitMQ preventing new flow for portal API sync to gateway proxy
Container portal_portal-data “API INFO” sends to container portal_rabbitmq - pushes updates to the proxy gateway
Reviewing the portal_portal-data log showed that the container FAILED to connect to portal_rabbitmq with ACCESS_REFUSED
LOG form portal-data
2023-03-30T19:07:37.023+00:00","[portal.log] [2023-03-30 19:07:37,022] [ERROR] [o.a.c.c.C.[.[.[.[dispatcherServlet]] [http-nio-8080-exec-10] [|] [|||] Servlet.service() for servlet [dispatcherServlet] in context with path [/portal-data] threw exception [Request processing failed; nested exception is com.layer7.portal.deployments.exceptions.DeploymentsException: Failed to send {} {} message to message sender for proxyUuid({}) of tenantId({}) : com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.] with root cause ",1
To resolve it we only needed to re-cycle the portal_portal-data container.
After the container was recycled to kick off Portal API deployments Toggle between Automatic and On Demand
Edit the proxy click On Demand, save, edit again, click Automatic then save
After this All Portal API sync to the gateway