Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 12773200C27 for ; Sun, 26 Feb 2017 21:39:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 110F0160B6E; Sun, 26 Feb 2017 20:39:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 33714160B5C for ; Sun, 26 Feb 2017 21:39:00 +0100 (CET) Received: (qmail 93240 invoked by uid 500); 26 Feb 2017 20:38:59 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 93229 invoked by uid 99); 26 Feb 2017 20:38:59 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Feb 2017 20:38:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F083DC127B for ; Sun, 26 Feb 2017 20:38:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id aee53zWsXu_I for ; Sun, 26 Feb 2017 20:38:58 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C4EBC5F23A for ; Sun, 26 Feb 2017 20:38:57 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 63E76E073C for ; Sun, 26 Feb 2017 20:38:46 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6563924140 for ; Sun, 26 Feb 2017 20:38:45 +0000 (UTC) Date: Sun, 26 Feb 2017 20:38:45 +0000 (UTC) From: "Murdo Aird (JIRA)" To: dev@brooklyn.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (BROOKLYN-444) Effector call works from GUI but fails from CLI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 26 Feb 2017 20:39:01 -0000 [ https://issues.apache.org/jira/browse/BROOKLYN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murdo Aird updated BROOKLYN-444: -------------------------------- Description: The following simple BP adds an Effector to an entity. The entity can be called from the web UI and succeeds. Drilling into the Activity logs shows the simple bash command works. However if I try to invoke the Effector via the CLI [1], the call fails: br app "effector-test" entity "Empty Software Process" effector DoStuff invoke For the CLI failure, it looks like a random (?) environment variable is being injected via the CLI [2]. {code:yaml} name: effector-test location: localhost services: - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess install.command: echo True launch.command: echo True checkRunning.command: echo true brooklyn.initializers: - type: org.apache.brooklyn.core.effector.ssh.SshCommandEffector brooklyn.config: name: DoStuff command: whoami {code} * Calling a standard Effector (e.g. stop) via the CLI works. * If the DoSuff Effector via CLI fails, I can subsequently call it from the web UI and it works Not to muddy the waters, but calling the same Effector from the REST API also results in an error - but it's a different one [3]. [1] https://gist.github.com/murdoaird/0ba46476b8ec1e5039097b3754f720f7 [2] https://gist.github.com/murdoaird/50777a5fa398a79611b4ec5bbfdc1d7d#env-1 [3] https://gist.github.com/murdoaird/e153c5b3502d5475dee7358e2d9c3472 was: The following simple BP adds an Effector to an entity. The entity can be called from the web UI and succeeds. Drilling into the Activity logs shows the simple bash command works. However if I try to invoke the Effector via the CLI [1], the call fails: br app "effector-test" entity "Empty Software Process" effector DoStuff invoke For the CLI failure, it looks like a random (?) environment variable is being injected via the CLI [2]. name: effector-test location: localhost services: - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess install.command: echo True launch.command: echo True checkRunning.command: echo true brooklyn.initializers: - type: org.apache.brooklyn.core.effector.ssh.SshCommandEffector brooklyn.config: name: DoStuff command: whoami * Calling a standard Effector (e.g. stop) via the CLI works. * If the DoSuff Effector via CLI fails, I can subsequently call it from the web UI and it works Not to muddy the waters, but calling the same Effector from the REST API also results in an error - but it's a different one [3]. [1] https://gist.github.com/murdoaird/0ba46476b8ec1e5039097b3754f720f7 [2] https://gist.github.com/murdoaird/50777a5fa398a79611b4ec5bbfdc1d7d#env-1 [3] https://gist.github.com/murdoaird/e153c5b3502d5475dee7358e2d9c3472 > Effector call works from GUI but fails from CLI > ----------------------------------------------- > > Key: BROOKLYN-444 > URL: https://issues.apache.org/jira/browse/BROOKLYN-444 > Project: Brooklyn > Issue Type: Bug > Affects Versions: 0.10.0 > Environment: Brooklyn Version 0.10.0 on Mac > Reporter: Murdo Aird > Priority: Critical > > The following simple BP adds an Effector to an entity. The entity can be called from the web UI and succeeds. Drilling into the Activity logs shows the simple bash command works. > However if I try to invoke the Effector via the CLI [1], the call fails: > br app "effector-test" entity "Empty Software Process" effector DoStuff invoke > For the CLI failure, it looks like a random (?) environment variable is being injected via the CLI [2]. > {code:yaml} > name: effector-test > location: localhost > services: > - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess > install.command: echo True > launch.command: echo True > checkRunning.command: echo true > brooklyn.initializers: > - type: org.apache.brooklyn.core.effector.ssh.SshCommandEffector > brooklyn.config: > name: DoStuff > command: whoami > {code} > * Calling a standard Effector (e.g. stop) via the CLI works. > * If the DoSuff Effector via CLI fails, I can subsequently call it from the web UI and it works > Not to muddy the waters, but calling the same Effector from the REST API also results in an error - but it's a different one [3]. > [1] https://gist.github.com/murdoaird/0ba46476b8ec1e5039097b3754f720f7 > [2] https://gist.github.com/murdoaird/50777a5fa398a79611b4ec5bbfdc1d7d#env-1 > [3] https://gist.github.com/murdoaird/e153c5b3502d5475dee7358e2d9c3472 -- This message was sent by Atlassian JIRA (v6.3.15#6346)