You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/04/27 17:16:04 UTC
[jira] [Commented] (BROOKLYN-339) Node.js entity fails
[ https://issues.apache.org/jira/browse/BROOKLYN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987064#comment-15987064 ]
Aled Sage commented on BROOKLYN-339:
------------------------------------
I was able to reproduce this with:
{noformat}
location:
aws-ec2:eu-west-1:
osFamily: centos
osVersion: 6.*
services:
- type: brooklyn-nodejs-application
{noformat}
The error is valid: it expects one of {{gitRepoUrl}} or {{archiveUrl}} to be specified.
If one deploys the app below, then it works:
{noformat}
location:
aws-ec2:eu-west-1:
osFamily: centos
osVersion: 6.*
services:
- type: brooklyn-nodejs-application
brooklyn.config:
nodejs.gitRepo.url: https://github.com/iyovcheva/dummy-repo.git
nodejs.app.name: dummy-app
nodejs.app.command: node app.js
{noformat}
There is room for improvement (e.g. we could fail-fast rather than provisioning the VM before failing).
However, closing this issue as it is not a bug. Please open an "improvement" if you think we should improve the error reporting or anything else.
> Node.js entity fails
> --------------------
>
> Key: BROOKLYN-339
> URL: https://issues.apache.org/jira/browse/BROOKLYN-339
> Project: Brooklyn
> Issue Type: Bug
> Environment: Tested on Centos 6 on AWS
> Reporter: Duncan Godwin
>
> Starting the Node.js entity gives the following error during the customize phase:
> {code}
> Failed after 0ms: At least one of Git or archive URL must be set for NodeJsWebAppServiceImpl{id=v9qctusjsb}
> java.lang.IllegalStateException: At least one of Git or archive URL must be set for NodeJsWebAppServiceImpl{id=v9qctusjsb}
> at org.apache.brooklyn.entity.webapp.nodejs.NodeJsWebAppSshDriver.customize(NodeJsWebAppSshDriver.java:131)
> at org.apache.brooklyn.entity.software.base.AbstractSoftwareProcessDriver$3$2.run(AbstractSoftwareProcessDriver.java:175)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at org.apache.brooklyn.util.core.task.DynamicSequentialTask$DstJob.call(DynamicSequentialTask.java:359)
> at org.apache.brooklyn.util.core.task.BasicExecutionManager$SubmissionCallable.call(BasicExecutionManager.java:519)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Note that running the Node.js tests DOES work, just not the entity on it's own
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)