pwplusnick opened a new issue #163: Knative implementation returns init 
response on non-stem cell first runs
URL: https://github.com/apache/openwhisk-runtime-nodejs/issues/163
 
 
   On the first run of non-stem cell (environmentally initialized containers), 
return the initialization response rather than the return of the run.
   
   Replication steps:
   service.yaml:
   ```yaml
   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: greetings-builtin-code
     namespace: default
   spec:
     template:
       spec:
         containers:
           - image: openwhisk/action-nodejs-v12
             env:
               - name: __OW_RUNTIME_PLATFORM
                 value: knative
               - name: __OW_ACTION_NAME
                 value: greetings-builtin-code
               - name: __OW_ACTION_CODE
                 value: "function main(params) {return {payload: 'Hello ' + 
params.name + ' from ' + params.place +  '!'};}"
   ```
   After deployment,
   ```bash
   kubectl apply -f service.yaml
   ```
   ```bash
   service.serving.knative.dev/greetings-builtin-code configured
   ```
   ```bash
   kubectl get ksvc
   ```
   ```bash
   NAME                     URL                                                 
LATESTCREATED                  LATESTREADY                    READY   REASON
   greetings-builtin-code   http://greetings-builtin-code.default.example.com   
greetings-builtin-code-fv6cv   greetings-builtin-code-fv6cv   True    
   ```
   value-data.json
   ```json
   {
       "value": {
           "name" : "Will",
           "place" : "Austin"
       }
   }
   ```
   Now when curl'ing the endpoint, we expect to see the function run
   ```bash
    curl -d @value-data.json http://greetings-builtin-code.default.example.com
   ```
   instead we see
   ```json
   {"OK":true}
   ```
   I can potentially look into the fix, but I definitely wanted to write down 
the replication steps before I forgot.
   <!--
   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:
   
   * local deployment, vagrant, native ubuntu, Mac OS, Bluemix, ...   
   * version of docker, vagrant, ubuntu, ...
   
   ## Steps to reproduce the issue:
   
   1.   
   2.   
   3.   
   
   
   ## Provide the expected results and outputs:
   
   ```
   output comes here
   ```
   
   
   ## Provide the actual results and outputs:
   
   ```
   output comes here
   ```
   
   ## Additional information you deem important:
   * issue happens only occasionally or under certain circumstances   
   * changes you did or observed in the environment
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to