I have an existing cluster which has a number of recipes attached to various instances. Some of the recipes need to be modified so that when a new instance is scaled up, it comes up with updated values/settings/etc. I'll also need to know how to attach new recipes to instances so again, when they get scaled up the will have the new recipes attached.   ... View more

We had attempted to repair a cluster after one of our nodes went into a bad state due to an issue with AWS. I ran the following command: cb cluster repair --name <cluster> --host-groups <host_groups> What I'm seeing now is that cloudbreak seems to be stick in a loop where we're seeing the following: cloudbreak_1   | 2019-05-21 13:30:21,119 [reactorDispatcher-68] pollWithTimeout:32 INFO  c.s.c.s.PollingService - [owner:6476a4d7-bab8-4bf9-bfcd-aa6a43aa1d5f] [type:CLUSTER] [id:2] [name:emea-hdp] [flow:438c526a-325b-40c8-b86a-cc15aad4728a] [tracking:669a1784-a361-4509-9cd2-c57847a15cbb] Polling attempt 16277. cloudbreak_1   | 2019-05-21 13:30:21,134 [reactorDispatcher-68] checkStatus:48 INFO  c.s.c.s.c.f.AmbariOperationsStatusCheckerTask - [owner:6476a4d7-bab8-4bf9-bfcd-aa6a43aa1d5f] [type:CLUSTER] [id:2] [name:<cluster>] [flow:438c526a-325b-40c8-b86a-cc15aad4728a] [tracking:669a1784-a361-4509-9cd2-c57847a15cbb] Ambari operation: 'Stopping components on the decommissioned hosts', Progress: 0 uluwatu_1      | 2019-05-21T13:30:21.141Z INFO [owner: ] [email: ] /notification endpoint:  {"eventType":"STOP_SERVICES_AMBARI_PROGRESS_STATE","eventTimestamp":1558445421137,"eventMessage":"0","owner":null,"account":null,"userIdV3":"email@email.com","cloud":"AWS","region":"eu-central-1","availabilityZone":null,"blueprintId":null,"blueprintName":null,"clusterId":2,"clusterName":"<cluster>","stackId":2,"stackName":"<cluster>","stackStatus":"AVAILABLE","nodeCount":null,"instanceGroup":null,"clusterStatus":"UPDATE_IN_PROGRESS","workspaceId":1} cb cluster list shows the following: [   {     "Name": "<cluster>",     "Description": "",     "CloudPlatform": "AWS",     "StackStatus": "AVAILABLE",     "ClusterStatus": "UPDATE_IN_PROGRESS"   } ] At this point we'd just like to stop the action and go back to a normal state. Any advice would be great. ... View more

We have noticed some strange behaviour in deploying HDP stacks with Cloudbreak. CB 2.7 HDP 2.6.5.0-292 Ambari: 2.6.2.0 Our scenario: 1. Cluster was already deployed and in a running state 2. We manually added some RPM's to one of the instances and added an iam role to the instance 3. Shut down the instances through CB and then shut down Cloudbreak (cbd kill) 4. Brought CB back up (cbd restart) 5. Brought the instances back up though CB At this point, all of the instances that had the RPM's added were terminated and redeployed, no obvious logs from CB. This ended up breaking everything since one of them was Ambari. Is this expected behaviour from CB? If so, how do we manage customization on the instances? One example would be RPM's that need to be updated on some of the instances. ... View more