@Jonathan Hurley: The error I'm getting in the Postfix log: warning: TLS library problem: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown:s3_pkt.c:1315:SSL alert number 46: The solution you suggest is exactly what I was looking for. I'll test and report back. ... View more

You can do that logged in with the previous admin user in the UI, clicking on the invited user: Hope this helps! ... View more

Hi @Peter Teunissen I have checked and the image exist in the storage account, link to that: https://sequenceiqwesteurope2.blob.core.windows.net/images/hdc-hdp--1703101455.vhd Could it be possible that your deployment is not able to reach the vhd because of some custom security rule? Have you tried install a cluster again maybe just some Azure service was unavailable that time? Br, Tamas ... View more

Then unfortunately this is something out of our reach. You might try setting up an external SMTP service. Hope this helps! ... View more

I could get a step further by manually updating the cluster status in the status table to 'STOPPED' manually starting all node vm's, logging in and halting them restarting cloudbreak Then after some time cloudbreak syncs with the cluster and can startup the cluster. However it says that the infrastructure is started and that a cluster startup is ongoing. In Azure however the VM's still have a 'stopped' status. When I look in the Cloudbreak startup log, I see an error: Failed to convert from type [java.util.LinkedHashSet<?>] to type [com.sequenceiq.cloudbreak.api.model.AutoscaleStackResponse] for value 'com.sequenceiq.cloudbreak.domain.Stack@25194c0b' Even after restarting Cloudbreak, these errors reoccur and the GUI still hangs in the 'update in progress: Starting Ambari cluster' fase... ... View more

I can stop & start just fine (apart from a small Zeppelin issue, but that's beside the point). ... and after some time and a logout/login, the node counts were updated correctly... all's good now. ... View more

I think this is an Ambari bug. You can report the issue here after you've registered: http://issues.apache.org/jira/browse/AMBARI . Also could you please accept the answer here so others can find the solution while it's beeing fixed. Thank you. Br, Krisz ... View more

Thanks @pdarvasi, that solved the issue. It was indeed the fact that my user has multiple subscriptions and it switched to the wrong one. It would be a good thing if the tool is able to handle that correctly. Thanks for filing the issue. I also noted that the current script greps for 'data: Application Id:' but at least in the latest version of the Azure CLI it actually reads 'data: AppId:' in the output. This might require a change to the tool also. Thanks for the help! ... View more