Member since
03-17-2017
23
Posts
5
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1381 | 04-19-2017 01:11 PM |
05-10-2017
01:45 PM
That did the trick, thanks. Is it possible to give this new user the ability to admin existing users too?
... View more
05-10-2017
12:39 PM
1 Kudo
I have a Cloudbreak 1.14.1 install up and running. A new user was added through the 'Sign up' link, but it appears that creates a completely new environment since that user can't see the existing clusters and doesn't show up under 'accounts'. I would like to remove this user so the email can be used to subsequently add the user using the 'Invite user' button. How can I remove a user that I can't see under accounts?
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak
04-19-2017
01:11 PM
It turned out that during moving the resources to another subscription, the storageaccount was inadvertently moved to another resource group. Moving it back solved the issue.
... View more
04-19-2017
09:58 AM
Immediately after starting the creation of my cluster the infrastructure creation fails due to a vhd file not found error: 4/19/2017 11:33:58 AM spark-dev - update in progress: Infrastructure creation failed. Reason: Image creation failed because https://sequenceiqwesteurope2.blob.core.windows.net/images/hdc-hdp--1703101455.vhddoes not exist or Cloudbreak could not reach. However, I created a similar cluster just weeks ago with the same setup If I go into the Cloudbreak VM and try to get the vhd URI with wget, I can simply download the vhd file. When I look in the Cloudbreak log, I see an additional error, just before the above: "The Resource 'Microsoft.Storage/storageAccounts/cbstorewe5db978ee37d347a' under resource group 'cbstore' was not found." When I look in Azure, I don't see this resource and I don't remember having seen it before. I'm running Cloudbreak version 1.14.1-6ff7af8 What could cause this problem? Could it be the missing resource? If so, how could I recreate it?
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak
03-29-2017
09:56 AM
1 Kudo
I had a working Cloudbreak 1.6.3 setup using Azure. After upgrading to 1.14.0, the credentials no longer work. Both an existing credential and newly created ones give the following error when creating a new cluster: Failed to create cluster: Unrecognized fiels 'tenantid' (class com.sequenceid.cloudbreak.api.model.wasbFileSystemConfigu[not visible in popup] not marked as ignorable (2 known properties: "accountname", "accountKey"]) as [Source: {"tenantid":"<removed>","clientid":"<removed>","accountname":"someaccount","accountKey":"<removed>" etc etc. The GUI provides an alternative way now to create an Azure credential (interactive) but that requires one to add subscriptionId and tenantid to 'profile', but there's no option in the GUI to update a 'profile'. I seems something is changed in the Azure credential setup, but only halfway released. What can I do to get a working credential and create a cluster?
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak
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-27-2017
09:33 AM
@khorvath Oops, I was a bit to enthusiastic... now Cloudbreak syncs without any errors, but it shows a count of 0 for each of the node types. In the header the total node count is still correct (5) but on the node type tabs it says 0 Under the Nodes sub page all nodes are shown as healthy. I checked, all the nodes are active in Ambari. It might be just cosmetic... but it's strange.
... View more
03-27-2017
09:23 AM
Thanks @khorvath, that worked flawlessly!
... View more
03-27-2017
08:52 AM
I have created a cluster on Azure using Cloudbreak. Due to access right issues in the Azure tenant, the cluster was moved to another Azure subscription. All is running just fine and shows up in the Azure portal under the new subscription. However, Cloudbreak has lost it's connection to the cluster due to the changed subscription ID. Syncing Cloudbreak to the cluster obviously fails currently. The GUI doesn't allow me to update an existing subscription ID within the credential. Is there another way for me to update the existing credential and sync Cloudbreak to the moved cluster?
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak
03-23-2017
07:01 PM
Thanks, that did the trick. I guess this is a bug. Where should I report it? A quick google search didn't give me anything useful on 'hortonworks bug report'
... View more