juju agent stuck initializing for subordinate charms

While setting relations for all the LMA stack to the Openstack services, 2 units got stuck with agents initializing for filebeat and telegraf.

The issue occurred on 1 of 3 heat units and 1 of 3 rabbitmq units.

I've been troubleshooting on the heat charm to avoid making any changes to the rabbitmq service.

I've rebooted the heat machine hosting the heat unit with the issue as well as remove the relation for heat and telegraf and heat and filebeat. This removed the subordinate charms from the other 2 of 3 heat units with no issues but the heat unit with the stuck agent would not remove the subordinate charm.

We believe this issue is related to load on the controller as we added all the relations for the LMA stack at once.

The current workaround was to make sure the unit was not the heat leader and removed the unit. Once the unit was re-added the agents initialized correctly. We are hesitant to do this with the rabbitmq unit with the same issue as we don't know of the performance impact to the cloud.