rads18 opened a new issue #4962: URL: https://github.com/apache/openwhisk/issues/4962
<!-- We use the issue tracker for bugs and feature requests. For general questions and discussion please use http://slack.openwhisk.org/ or https://openwhisk.apache.org/contact.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: *Kubernetes, kubernetes 1.13 Docker version 18.09.7 ## Steps to reproduce the issue: 1. Changed the default max for memory and time as below: actions: time: min: "100ms" #LT: Updated #max: "5m" **max: "15m"** #LT std: "1m" memory: min: "128m" #LT: Updated #max: "512m" **max: "1024m"** #LT std: "256m" 2. Post change create or update any function (python3) to use new max Like change the function to use "-m 768" or '-m 1024" . The function fails to work and errors out with response "response": { "status": "whisk internal error", "statusCode": 0, "success": false, "result": { "error": "Action version is not compatible and cannot be invoked." } } 3. However, updating the function back to the old max still works. 4. There are no errors in updating function to the new max memory number only when invoking the function it fails. 5. invoker was restarted as per my knowledge but no difference. ## Provide the expected results and outputs: ``` The function should be transparent to this memory update ``` ## Provide the actual results and outputs: ``` output comes here ``` ## Additional information you deem important: * The issue is persistent once the action is updated to use any value above the previous max 512 Also as i pointed above the issue is fixed when the function is updated back to use any value under or equal to the old max 512 ---------------------------------------------------------------- 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: [email protected]
