We are aware of some performance issues with Azure when initializing the cluster, causing the cluster initialization to time out. Only in a rare set of cases, the cluster creation actually fails, since in most cases it just takes more time than expected to initialize.
We have planned to work on fixing these issues soon, but unfortunately can't give an estimation for when that will happen.
We recommend you to re-deploy the cluster again (remove the old cluster and re-create it), due to it not having started properly.
If that is not possible (e.g. you already have data in the cluster and do not want to migrate), we recommend you to check the "/opt/bitnami/var/log/first-boot.log" log for what action failed (e.g. even if the wait for seeds timed out it might have continued performing actions to initialize the cluster).
Also, if you see any file matching the
/tmp/nami* pattern, it would be nice to know if there is any error there.
That way we might be able to help you fix the cluster without needing to re-deploy. However, re-reploying is a lot faster which is why we recommend following this road before that.