Member since
03-17-2017
23
Posts
5
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1506 | 04-19-2017 01:11 PM |
05-10-2017
02:24 PM
You can do that logged in with the previous admin user in the UI, clicking on the invited user: Hope this helps!
... View more
04-19-2017
03:05 PM
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
03-29-2017
10:24 AM
1 Kudo
Hi, please upgrade to 1.14.1 (not relased yet). This issue has been fixed in this version. curl -Ls s3://public-repo-1.hortonworks.com/HDP/cloudbreak/cloudbreak-deployer_1.14.1_Linux_x86_64.tgz | sudo tar -xz -C /bin cbd
cbd --version
cbd regenerate
cbd restart Anyway the Profile file is where you execute cbd commands. (/var/lib/cloudbreak-deployment for example)
... View more
03-27-2017
10:39 AM
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
03-23-2017
03:02 PM
Hi, 22 and 9443 must be open otherwise the provision will fail. 9443 is used with 2-way-ssl for CB to orchestrate the install.
... View more
03-23-2017
10:08 PM
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
03-17-2017
11:03 PM
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