[GitHub] bwmcadams opened a new issue #3439: KubernetesContainer doesn't properly track the timestamp, leading to logging problems esp. under load

[GitBox <gi...@apache.org>]

bwmcadams opened a new issue #3439: KubernetesContainer doesn't properly track the timestamp, leading to logging problems esp. under load
URL: https://github.com/apache/incubator-openwhisk/issues/3439
 
 
   <!--
   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/incubator-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:
   
   * OpenWhisk running on Kubernetes
   * all versions of Kubernetes
   
   ## Steps to reproduce the issue:
   
   1.   Start up OpenWhisk against Kubernetes (or OpenShift, which uses it behind the scenes)
   2.   Make a number of repeated requests to an endpoint
   3.   Request the activation logs
   
   
   ## Provide the expected results and outputs:
   
   The results should, if it is an endpoint with output, show the output.
   
   ```
   $ ACTIVATION_ID=$(wsk action -i invoke --blocking hello | tail -n +2 | jq .activationId | sed 's/"//g' ) && sleep 1.50 && wsk activation -i logs $ACTIVATION_ID
   2018-03-13T21:06:34.652259951Z stdout: hello, undefined!
   ```
   
   
   ## Provide the actual results and outputs:
   
   The failure is intermittent, but frequent…
   ```
   $ ACTIVATION_ID=$(wsk action -i invoke --blocking hello | tail -n +2 | jq .activationId | sed 's/"//g' ) && sleep 1.50 && wsk activation -i logs $ACTIVATION_ID
   error: Unable to get logs for activation 'f0298257c9a644dda98257c9a674dd09': The requested resource does not exist. (code 18950)
   ```
   
   ## Additional information you deem important:
   * There is an additional minor, related issue where if the Kubernetes log handler returns no logs (typically because of the main issue), it may fail to handle that properly and cause more downstream issues. This is also problematic if you manage to request logs before Kubernetes makes them available. The fix is to retry.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services