<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Can Cloudbreak deploy HDP on custom AMI's? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145393#M107961</link>
    <description>&lt;P&gt;This worked on v1.3. Thank you so much, &lt;A rel="user" href="https://community.cloudera.com/users/258/rdoktorics.html" nodeid="258"&gt;@rdoktorics&lt;/A&gt;!&lt;/P&gt;&lt;P&gt;I also was able to use the modified aws-images.yml file on the latest build of master without changing any Profile or config, so that can be an option for us to consider as well.&lt;/P&gt;&lt;P&gt;Also, is there any documentation for how to pre-configure an AMI for Cloudbreak to be able to deploy nodes successfully? Does it handle the standard HDP pre-config steps at all? We'd like to use RHEL, if possible.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jul 2016 02:18:06 GMT</pubDate>
    <dc:creator>mjrhee</dc:creator>
    <dc:date>2016-07-27T02:18:06Z</dc:date>
    <item>
      <title>Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145389#M107957</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would like Cloudbreak to use a custom AMI for my HDP nodes on AWS, but there doesn't seem to be a way to do this in the UI or shell. Is there a way to do this using the API? Or some other potential route? What kinds of pre-configuration are required?&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Sun, 24 Jul 2016 19:01:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145389#M107957</guid>
      <dc:creator>mjrhee</dc:creator>
      <dc:date>2016-07-24T19:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145390#M107958</link>
      <description>&lt;P&gt;Hi @mjrhee,&lt;/P&gt;&lt;P&gt; Cloudbreak shell now part of the cloudbreak repository here: &lt;A href="https://github.com/sequenceiq/cloudbreak/tree/master/shell" target="_blank"&gt;https://github.com/sequenceiq/cloudbreak/tree/master/shell&lt;/A&gt;
and this repository &lt;A href="https://github.com/sequenceiq/cloudbreak-shell" target="_blank"&gt;https://github.com/sequenceiq/cloudbreak-shell&lt;/A&gt; is no longer supported (also the --image tag) as the README mention.
Currently you can define custom image with this process: &lt;A href="http://sequenceiq.com/cloudbreak-docs/master/images/" target="_blank"&gt;http://sequenceiq.com/cloudbreak-docs/master/images/&lt;/A&gt;
If you need any other information just let me know. &lt;/P&gt;&lt;P&gt;Br, &lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 20:09:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145390#M107958</guid>
      <dc:creator>rdoktorics</dc:creator>
      <dc:date>2016-07-25T20:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145391#M107959</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/258/rdoktorics.html" nodeid="258"&gt;@rdoktorics&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Thanks for the tip. I have tried creating and editing the etc/aws-images.yml file as the docs describe, stopped and restarted Cloudbreak, but it's still defaulting to the same AMI as before (us-west-1:ami-3a750e5a).&lt;/P&gt;&lt;P&gt;From what I can tell, the AMI is pulled into the code when the application is built. See here: &lt;A href="https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/aws-images.tmpl"&gt;https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/aws-images.tmpl&lt;/A&gt;  and &lt;A href="https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/src/main/resources/aws-images.yml"&gt;https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/src/main/resources/aws-images.yml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In my case, Cloudbreak always uses the AMI defined in version 55 of this atlas: &lt;A href="https://atlas.hashicorp.com/api/v1/artifacts/sequenceiq/cloudbreak/amazon.image/search"&gt;https://atlas.hashicorp.com/api/v1/artifacts/sequenceiq/cloudbreak/amazon.image/search&lt;/A&gt;&lt;/P&gt;&lt;P&gt;FYI, I am using the pre-built cloud image of Cloudbreak 1.3 in us-west-1 on AWS. Is there something else I'm missing?&lt;/P&gt;&lt;P&gt;Best,
Michael&lt;/P&gt;&lt;P&gt;*EDIT: Added Cloudbreak version for clarity.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 23:18:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145391#M107959</guid>
      <dc:creator>mjrhee</dc:creator>
      <dc:date>2016-07-25T23:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145392#M107960</link>
      <description>&lt;P&gt;Could you please add this line to your Profile: 
&lt;STRONG&gt;export CBD_FORCE_START=true&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;and also please write this into the compose file where the cloudbreak container is declared under the volume definition:&lt;/P&gt;&lt;P&gt;- ./etc/:/etc/cloudbreak&lt;/P&gt;&lt;P&gt;after the modification the volume section will seems like this:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;volumes:&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;&lt;EM&gt;- "/Users/rdoktorics/Projects/cloudbreak-deployer/certs:/certs"&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;&lt;EM&gt;- /dev/urandom:/dev/random&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;&lt;EM&gt;- ./etc/:/etc/cloudbreak&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;

after that please &lt;STRONG&gt;do not&lt;/STRONG&gt; regenerate the compose file. This is just a patch because cbd 1.3.0 does not implement this feature. The future releases will contains this fix.&lt;/P&gt;&lt;P&gt;If you have any problem applying the patch then I am happy to help on webex.&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2016 16:00:26 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145392#M107960</guid>
      <dc:creator>rdoktorics</dc:creator>
      <dc:date>2016-07-26T16:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145393#M107961</link>
      <description>&lt;P&gt;This worked on v1.3. Thank you so much, &lt;A rel="user" href="https://community.cloudera.com/users/258/rdoktorics.html" nodeid="258"&gt;@rdoktorics&lt;/A&gt;!&lt;/P&gt;&lt;P&gt;I also was able to use the modified aws-images.yml file on the latest build of master without changing any Profile or config, so that can be an option for us to consider as well.&lt;/P&gt;&lt;P&gt;Also, is there any documentation for how to pre-configure an AMI for Cloudbreak to be able to deploy nodes successfully? Does it handle the standard HDP pre-config steps at all? We'd like to use RHEL, if possible.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 02:18:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145393#M107961</guid>
      <dc:creator>mjrhee</dc:creator>
      <dc:date>2016-07-27T02:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145394#M107962</link>
      <description>&lt;P&gt;You should contact with the Hortonworks support and they will help you to create the custom AMI's.&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Richard &lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 15:14:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145394#M107962</guid>
      <dc:creator>rdoktorics</dc:creator>
      <dc:date>2016-07-28T15:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145395#M107963</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I followed the instructions, and added my ami in the etc/aws-images.yml.&lt;/P&gt;&lt;P&gt;I did see the HDP/Ambari VMs were created from the image. But I got timeout error when cloudbreak ssh into the VM.&lt;/P&gt;&lt;P&gt;Error logs from cloudbreak&lt;/P&gt;&lt;PRE&gt;/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,899 [reactorDispatcher-37] checkStatus:31 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Connecting with ssh
to: 52.8.62.29, user: ec2-user, privatekey: /certs/stack-3/cb-ssh-key-3
/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,941 [reactorDispatcher-37] checkStatus:37 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Failed to connect ss
h: Exhausted available authentication methods
/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,941 [reactorDispatcher-37] notifyDisconnect:75 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Disconnected - BY_AP
PLICATION
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,961 [reactorDispatcher-37] pollWithTimeout:30 ESC[34mINFO ESC[0;39m c.s.c.s.PollingService - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Polling attempt 99.
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,963 [reactorDispatcher-37] init:155 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Client identity string: SSH-2.0
-SSHJ_0_14_0
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,968 [reactorDispatcher-37] init:168 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Server identity string: SSH-2.0
-OpenSSH_5.3
&lt;/PRE&gt;&lt;PRE&gt;/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,032 [reactorDispatcher-37] checkStatus:31 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Connecting with ssh
to: 52.8.62.29, user: ec2-user, privatekey: /certs/stack-3/cb-ssh-key-3
/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,075 [reactorDispatcher-37] checkStatus:37 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Failed to connect ss
h: Exhausted available authentication methods
/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,075 [reactorDispatcher-37] notifyDisconnect:75 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Disconnected - BY_AP
PLICATION
/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,095 [reactorDispatcher-37] pollWithTimeout:55 ESC[34mINFO ESC[0;39m c.s.c.s.PollingService - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Poller timeout.
/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,096 [reactorDispatcher-37] execute:73 ESC[1;31mERRORESC[0;39m c.s.c.c.f.AbstractAction - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Error during execution o
f com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6
/cbreak_cloudbreak_1 | com.sequenceiq.cloudbreak.service.CloudbreakServiceException: Operation timed out. Could not reach ssh connection in time
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.SshCheckerTask.handleTimeout(SshCheckerTask.java:50)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.SshCheckerTask.handleTimeout(SshCheckerTask.java:14)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.PollingService.pollWithTimeout(PollingService.java:56)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.PollingService.pollWithTimeoutSingleFailure(PollingService.java:66)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.TlsSetupService.waitForSsh(TlsSetupService.java:103)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.TlsSetupService.setupTls(TlsSetupService.java:83)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationService.setupTls(StackCreationService.java:163)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6.doExecute(StackCreationActions.java:160)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6.doExecute(StackCreationActions.java:157)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.AbstractAction.execute(AbstractAction.java:70)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.state.ObjectState.entry(ObjectState.java:135)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.entryToState(AbstractStateMachine.java:860)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.setCurrentState(AbstractStateMachine.java:704)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.switchToState(AbstractStateMachine.java:628)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.access$200(AbstractStateMachine.java:80)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine$2.transit(AbstractStateMachine.java:274)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.handleTriggerTrans(DefaultStateMachineExecutor.java:204)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.processTriggerQueue(DefaultStateMachineExecutor.java:342)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.access$100(DefaultStateMachineExecutor.java:57)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor$1.run(DefaultStateMachineExecutor.java:231)
/cbreak_cloudbreak_1 |  at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.scheduleEventQueueProcessing(DefaultStateMachineExecutor.java:243)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.execute(DefaultStateMachineExecutor.java:141)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.sendEvent(AbstractStateMachine.java:201)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.FlowAdapter.sendEvent(FlowAdapter.java:54)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.Flow2Handler.accept(Flow2Handler.java:74)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.Flow2Handler.accept(Flow2Handler.java:23)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:317)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:310)
/cbreak_cloudbreak_1 |  at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72)
/cbreak_cloudbreak_1 |  at reactor.bus.routing.TraceableDelegatingRouter.route(TraceableDelegatingRouter.java:51)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:591)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:63)
/cbreak_cloudbreak_1 |  at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160)
/cbreak_cloudbreak_1 |  at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74)
/cbreak_cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
/cbreak_cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
/cbreak_cloudbreak_1 |  at java.lang.Thread.run(Thread.java:745)
/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,096 [reactorDispatcher-37] sendEvent:103 ESC[34mINFO ESC[0;39m c.s.c.c.f.AbstractAction - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Triggering event: com.sequenceiq.cloudbreak.reactor.api.event.StackFailureEvent@64fde9f1
&lt;/PRE&gt;&lt;P&gt;If I use the default ami, everything is ok. My cloudbreak version is 1.5.0-rc.9-371eb32&lt;/P&gt;&lt;P&gt;I used packer to build my image from official CentOS6, and I did set the ec2-user as default ssh user.&lt;/P&gt;&lt;P&gt;Not sure what special setup need in the ami?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Wendell&lt;/P&gt;,,&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I followed the instructions, added the etc/aws-images.yml with my ami.&lt;/P&gt;&lt;P&gt;I did see the image is used and deployed as HDP/Ambari VMs. But I got the time out error when cloudbreak ssh into the VM.&lt;/P&gt;&lt;PRE&gt;/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,899 [reactorDispatcher-37] checkStatus:31 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Connecting with ssh
to: 52.8.62.29, user: ec2-user, privatekey: /certs/stack-3/cb-ssh-key-3
/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,941 [reactorDispatcher-37] checkStatus:37 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Failed to connect ss
h: Exhausted available authentication methods
/cbreak_cloudbreak_1 | 2016-09-05 18:02:54,941 [reactorDispatcher-37] notifyDisconnect:75 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Disconnected - BY_AP
PLICATION
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,961 [reactorDispatcher-37] pollWithTimeout:30 ESC[34mINFO ESC[0;39m c.s.c.s.PollingService - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Polling attempt 99.
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,963 [reactorDispatcher-37] init:155 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Client identity string: SSH-2.0
-SSHJ_0_14_0
/cbreak_cloudbreak_1 | 2016-09-05 18:02:59,968 [reactorDispatcher-37] init:168 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Server identity string: SSH-2.0
-OpenSSH_5.3
/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,032 [reactorDispatcher-37] checkStatus:31 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Connecting with ssh
to: 52.8.62.29, user: ec2-user, privatekey: /certs/stack-3/cb-ssh-key-3
/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,075 [reactorDispatcher-37] checkStatus:37 ESC[34mINFO ESC[0;39m c.s.c.s.s.f.SshCheckerTask - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Failed to connect ss
h: Exhausted available authentication methods
/cbreak_cloudbreak_1 | 2016-09-05 18:03:00,075 [reactorDispatcher-37] notifyDisconnect:75 ESC[34mINFO ESC[0;39m n.s.s.t.TransportImpl - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Disconnected - BY_AP
PLICATION&lt;/PRE&gt;&lt;PRE&gt;/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,095 [reactorDispatcher-37] pollWithTimeout:55 ESC[34mINFO ESC[0;39m c.s.c.s.PollingService - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Poller timeout.
/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,096 [reactorDispatcher-37] execute:73 ESC[1;31mERRORESC[0;39m c.s.c.c.f.AbstractAction - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Error during execution o
f com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6
/cbreak_cloudbreak_1 | com.sequenceiq.cloudbreak.service.CloudbreakServiceException: Operation timed out. Could not reach ssh connection in time
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.SshCheckerTask.handleTimeout(SshCheckerTask.java:50)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.SshCheckerTask.handleTimeout(SshCheckerTask.java:14)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.PollingService.pollWithTimeout(PollingService.java:56)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.PollingService.pollWithTimeoutSingleFailure(PollingService.java:66)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.TlsSetupService.waitForSsh(TlsSetupService.java:103)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.service.stack.flow.TlsSetupService.setupTls(TlsSetupService.java:83)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationService.setupTls(StackCreationService.java:163)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6.doExecute(StackCreationActions.java:160)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationActions$6.doExecute(StackCreationActions.java:157)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.AbstractAction.execute(AbstractAction.java:70)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.state.ObjectState.entry(ObjectState.java:135)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.entryToState(AbstractStateMachine.java:860)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.setCurrentState(AbstractStateMachine.java:704)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.switchToState(AbstractStateMachine.java:628)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.access$200(AbstractStateMachine.java:80)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine$2.transit(AbstractStateMachine.java:274)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.handleTriggerTrans(DefaultStateMachineExecutor.java:204)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.processTriggerQueue(DefaultStateMachineExecutor.java:342)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.access$100(DefaultStateMachineExecutor.java:57)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor$1.run(DefaultStateMachineExecutor.java:231)
/cbreak_cloudbreak_1 |  at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.scheduleEventQueueProcessing(DefaultStateMachineExecutor.java:243)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.DefaultStateMachineExecutor.execute(DefaultStateMachineExecutor.java:141)
/cbreak_cloudbreak_1 |  at org.springframework.statemachine.support.AbstractStateMachine.sendEvent(AbstractStateMachine.java:201)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.FlowAdapter.sendEvent(FlowAdapter.java:54)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.Flow2Handler.accept(Flow2Handler.java:74)
/cbreak_cloudbreak_1 |  at com.sequenceiq.cloudbreak.core.flow2.Flow2Handler.accept(Flow2Handler.java:23)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:317)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:310)
/cbreak_cloudbreak_1 |  at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72)
/cbreak_cloudbreak_1 |  at reactor.bus.routing.TraceableDelegatingRouter.route(TraceableDelegatingRouter.java:51)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:591)
/cbreak_cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:63)
/cbreak_cloudbreak_1 |  at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160)
/cbreak_cloudbreak_1 |  at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74)
/cbreak_cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
/cbreak_cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
/cbreak_cloudbreak_1 |  at java.lang.Thread.run(Thread.java:745)
/cbreak_cloudbreak_1 | 2016-09-05 18:03:05,096 [reactorDispatcher-37] sendEvent:103 ESC[34mINFO ESC[0;39m c.s.c.c.f.AbstractAction - [owner:d1293e7e-a6fd-450c-bfb7-f42fa305a295] [type:STACK] [id:3] [name:spark2] Triggering event: com.sequenceiq.cloudbreak.reactor.api.event.StackFailureEvent@64fde9f1&lt;/PRE&gt;&lt;P&gt;But if I use the default ami, everything is ok. My cloudbreak version is 1.5.0-rc.9-371eb32&lt;/P&gt;&lt;P&gt;I used packer build the ami from official CentOS6, and do set the default ssh user as ec2-user.&lt;/P&gt;&lt;P&gt;So not sure what special setup need to be done in the ami?&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Wendell&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2016 03:38:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145395#M107963</guid>
      <dc:creator>wendell_bu</dc:creator>
      <dc:date>2016-09-06T03:38:17Z</dc:date>
    </item>
    <item>
      <title>Re: Can Cloudbreak deploy HDP on custom AMI's?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145396#M107964</link>
      <description>&lt;P&gt;With Cloudbreak 1.6.1, you can use Custom Cloud Images, which you can specify in the &lt;STRONG&gt;/etc/&lt;/STRONG&gt; directory, as mentioned in this document: &lt;A href="http://sequenceiq.com/cloudbreak-docs/latest/images/" target="_blank"&gt;http://sequenceiq.com/cloudbreak-docs/latest/images/&lt;/A&gt;. There's no need to modify the &lt;I&gt;Profile&lt;/I&gt; file.&lt;/P&gt;&lt;P&gt;If you add a custom AMI for AWS for example, remember to run &lt;EM&gt;&lt;STRONG&gt;cbd restart&lt;/STRONG&gt;&lt;/EM&gt; before deploying a cluster.&lt;/P&gt;&lt;P&gt;Cheers,
K&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 23:53:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-Cloudbreak-deploy-HDP-on-custom-AMI-s/m-p/145396#M107964</guid>
      <dc:creator>karri_linnoinen</dc:creator>
      <dc:date>2016-12-28T23:53:22Z</dc:date>
    </item>
  </channel>
</rss>

