Member since
11-09-2017
69
Posts
17
Kudos Received
13
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1153 | 04-05-2019 08:50 AM | |
933 | 04-04-2019 05:17 PM | |
1554 | 04-04-2019 05:08 PM | |
1391 | 09-11-2018 09:12 AM | |
2176 | 06-27-2018 03:11 PM |
04-05-2019
08:50 AM
Hi @Alexander Schätzle It's not possible to move a cluster around. A cluster have many resources linked to it, like credential, DB and kerberos configuration, etc. If you could move your cluster this would mean moving all of these too.
... View more
04-04-2019
05:17 PM
Hi @Margus Roo, It's not possible to import existing clusters. The only option is to restore the old Cloudbreak from backup.
... View more
04-04-2019
05:08 PM
1 Kudo
Hi @Alexander Schätzle, Unfortunately you can't add this on the UI. You can save the JSON and edit it and use the CLI. (although an unsupported way can be editing the request with some kind of browser extension like tampermonkey)
... View more
12-06-2018
10:10 AM
3 Kudos
The latest Docker version available form official Centos and RedHat repository has an issue preventing to exec the container. Issue when starting Cloudbreak is the following: Starting Cloudbreak generating docker-compose.yml generating uaa.yml Initialize and migrate databases Creating cbreak_commondb_1 ... Creating cbreak_commondb_1 ... done [ERROR] The database hasn't started within 30 seconds. Docker version: docker-1.13.1-84.git07f3374.el7.centos.x86_64 There are the following solutions, you can choose either: Downgrade to an older version: yum downgrade docker-1.13.1-75.git8633870.el7.centos.x86_64 docker-client-1.13.1-75.git8633870.el7.centos.x86_64 docker-common-1.13.1-75.git8633870.el7.centos.x86_64 Upgrade to a newer version, using Docker repository: https://docs.docker.com/install/linux/docker-ce/centos/#set-up-the-repository After choosing either option docker restart should work.
... View more
Labels:
09-13-2018
02:00 PM
Hi @Sebastian Hätälä CB support only AWS, Azure, GCP and OpenStack right now.
... View more
09-11-2018
09:12 AM
Hi @Jakub Igla, Could you install a cluster without CB managed Knox and add Knox service via Ambari? If it solves your problem I suggest you should use Knox gateway this way.
... View more
07-04-2018
02:34 PM
1 Kudo
Hi @Michael Young, It's a great article, I managed to apply the steps, but in my experience it would make it much easier if you would attach the files. Copying the text makes the spaces and tabs ambiguous. Thanks
... View more
06-28-2018
08:01 AM
Hi @Jakub Igla, Yes, a different thread for a different issue would be nice. Thanks
... View more
06-28-2018
06:06 AM
Hi @Jakub Igla, I'm glad to hear everything works. Don't forget to remove the DOCKER_TAG_CLOUDBREAK variable when you upgrade to a new version.
... View more
06-27-2018
04:02 PM
Hi @Jakub Igla, we had to deactivate setting example.com as the fallback domain for Azure, as there is an issue on Azure when sometimes we have to wait unknown time to get the domain name. In your case it looks like, that for private network with custom DNS this would never happen. I think you should try to set CB_HOST_DISCOVERY_CUSTOM_DOMAIN in your Profile under your deployment directory and restart cloudbreak with 'cbd restart': export CB_HOST_DISCOVERY_CUSTOM_DOMAIN=test.com This will setup all of your cluster with this domain. Hopefully it will override the waiting and you will have a functional cluster. Please let me know if this helped.
... View more