You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/18 10:38:41 UTC
[jira] [Commented] (BROOKLYN-475) VM provisioning fails for custom
AMI with extra stdout when ssh'ing
[ https://issues.apache.org/jira/browse/BROOKLYN-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972483#comment-15972483 ]
ASF GitHub Bot commented on BROOKLYN-475:
-----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/639
BROOKLYN-475: fix machine-details parsing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server BROOKLYN-475
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/639.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #639
----
commit ee0cabde0e2da32a5ba60c2312432baa3e847b25
Author: Aled Sage <al...@gmail.com>
Date: 2017-04-18T09:03:13Z
Renamed to MachineDetailsIntegrationTest
commit 2d165e2705532d6ae036fb76868a7f31cb573360
Author: Aled Sage <al...@gmail.com>
Date: 2017-04-18T10:35:48Z
BROOKLYN-475: fix machine-details parsing
----
> 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)