Update existing Azure credential with new subscription ID

[#1]

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?

[#2 · Accepted solution]

Hi,

Unfortunately in this case you can update the DB the following way:

docker exec -it cbreak_cbdb_1 psql -U postgres
select id,attributes from credential where cloudplatform='AZURE_RM';
update credential set attributes='XX' where id=X;

1st step to exec into the DB docker container

2nd to select the credential you want to update (please note the ID, and copy the whole attributes filed which you want to update)

3rd update the field with the desired changes (please make sure the formatting is correct and the same as before)

[#3]

Thanks @khorvath, that worked flawlessly!

[#4]

@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.

[#5]

Besides the UI weirdness can you for example stop/start your cluster with CB?

[#6]

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.