[
https://issues.apache.org/jira/browse/BROOKLYN-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972681#comment-15972681
]
ASF GitHub Bot commented on BROOKLYN-475:
-----------------------------------------
Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/639
Thanks @bostko - merging.
> VM provisioning fails for custom AMI with extra stdout when ssh'ing
> -------------------------------------------------------------------
>
> Key: BROOKLYN-475
> URL: https://issues.apache.org/jira/browse/BROOKLYN-475
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Aled Sage
>
> With 0.11.0 RC1, a customer is failing to deploy any entities when using a
> custom AMI in AWS.
> It seems that the VM writes out extra stdout when executing ssh commands,
> such as:
> {noformat}
> Last login: Fri Apr 14 08:01:37 2017 from 35.156.73.145
> {noformat}
> When attempting to provision an entity there, it fails with the error:
> {noformat}
> Chunk [Last login: Fri Apr 14 08:01:37 2017 from 35.156.73.145] is not a
> valid entry
> {noformat}
> I'm guessing this comes from:
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Chunk [Last login: Fri Apr 14
> 08:01:37 2017 from 35.156.73.145] is not a valid entry
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)
> at com.google.common.base.Splitter$MapSplitter.split(Splitter.java:512)
> at
> org.apache.brooklyn.core.location.BasicMachineDetails$1.apply(BasicMachineDetails.java:152)
> at
> org.apache.brooklyn.core.location.BasicMachineDetails$1.apply(BasicMachineDetails.java:1)
> at
> org.apache.brooklyn.util.core.task.system.ProcessTaskWrapper$ProcessTaskInternalJob.call(ProcessTaskWrapper.java:119)
> ... 5 more
> {noformat}
> which is executed when attempting to infer the OS details (by executing an
> ssh command on the VM).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
