Clients not recieving messages after re-connect to message broker

[robert-sanfeliu]

On nebulous-cd if the message broker gets restarted, all components that are using EXN middleware library become unresponsive.

Logs for the components show that the connection was lost, and the connection is restored (once message broker goes online again), but, after that, messages sent to the message broker won't be recieved by the subscribers.

For instance, EXN middleware component itself won't receive requests from GUI to register a new cloud provider. Althoug I have confirmed that the GUI sent a message to the message broker.

[robert-sanfeliu]

@fotisp after further investigation, me and several others have experienced this issue only when the whole nebulous-core is started. For instance, Francisco from Telefonica have their own installation of NebulOuS on a VM on AWS. When they start the VM to work during the day, they have to restart all components except message broker. We even came up with this command to make the process easier:
kubectl get pods -n $NEBULOUS_ENV --no-headers | xargs kubectl delete pod