mjblackhorse opened a new issue, #5376: URL: https://github.com/apache/openwhisk/issues/5376
<!-- We use the issue tracker for bugs and feature requests. For general questions and discussion please use https://openwhisk.apache.org/slack.html or https://openwhisk.apache.org/community.html instead. Do NOT share passwords, credentials or other confidential information. Before creating a new issue, please check if there is one already open that fits the defect you are reporting. If you open an issue and realize later it is a duplicate of a pre-existing open issue, please close yours and add a comment to the other. Issues can be created for either defects or enhancement requests. If you are a committer than please add the labels "bug" or "feature". If you are not a committer please make clear in the comments which one it is, so that committers can add these labels later. If you are reporting a defect, please edit the issue description to include the information shown below. If you are reporting an enhancement request, please include information on what you are trying to achieve and why that enhancement would help you. For more information about reporting issues, see https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#raising-issues Use the commands below to provide key information from your environment: You do not have to include this information if this is a feature request. --> ## Environment details: * I run openwhisk on a virtualbox VM on a workstation Workstation : * CUP : Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz 3.60 GHz * MEMORY: 32G * OS: Win10 Pro VM: * OS: Ubuntu 22.04.1 LTS (64 bits) * CPU: 1cpu * MEMEORY: 8G * version of docker, ubuntu, ... ``` shell Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy ``` Docker version 20.10.23, build 7155243 ## Steps to reproduce the issue: 1. code ``` node.js function main(args){ console.log(args.name) return {} } ``` 2. create package ``` shell $ wsk pakcage update basics ``` 3. create action ``` shell $ wsk action update basics/log-alpha -p name alpha log.js ``` 4. create a trigger ``` shell $ wsk trigger create basics-alert ``` 5. create a rule ``` shell $ wsk rule update basics-alert-alpha basics-alert basics/log-alpha ``` 6. fire the trigger ``` shell $ wsk trigger fire basics-alert $ ok: triggered /_/basics-alert with id 46a799668bd34138a799668bd3c138ce ``` 7. get result ``` shell $ wsk activation get 46a799668bd34138a799668bd3c138ce ``` ## Provide the expected results and outputs: The logs should provide something like ``` [ "2023-02-07T02:02:27.001323024Z alpha" ] ``` ## Provide the actual results and outputs: "There was an internal server error." when the rule is activated to invoke the action `basics/log-alpha` ``` { "namespace": "guest", "name": "basics-alert", "version": "0.0.1", "subject": "guest", "activationId": "46a799668bd34138a799668bd3c138ce", "start": 1675735493384, "end": 0, "duration": 0, "statusCode": 0, "response": { "status": "success", "statusCode": 0, "success": true, "result": {} }, "logs": [ "{\"statusCode\":3,\"success\":false,\"rule\":\"guest/basics-alert-alpha\",\"error\":\"There was an internal server error.\",\"action\":\"guest/basics/log-alpha\"}" ], "annotations": [], "publish": false } ``` ## Additional information you deem important: The openwhisk logs: ``` shell [2023-02-07T10:04:53.388Z] [INFO] [#tid_Wl0sjUAto0nZhXQkQzqvt2Cgy0Qs1V3c] [BasicHttpService] [marker:http_post.202_counter:14:14] [2023-02-07T10:04:53.447Z] [ERROR] [#tid_Wl0sjUAto0nZhXQkQzqvt2Cgy0Qs1V3c] [TriggersApi] trigger-fired action 'guest/basics/log-alpha' failed to invoke with akka.stream.StreamTcpException: Tcp command [Connect(localhost:3233,None,List(),Some(10 seconds),true)] failed because of java.net.ConnectException: Connection refused [2023-02-07T10:04:53.448Z] [INFO] [#tid_Wl0sjUAto0nZhXQkQzqvt2Cgy0Qs1V3c] [MemoryArtifactStore] [PUT] 'activations' saving document: 'id: guest/46a799668bd34138a799668bd3c138ce, rev: null' [marker:database_saveDocument_start:74] ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
