"error": "Failed to provision resources to run the action."

[liusy58]

Hi, sir, every time I create an action successfully but once I invoke the action I would got the error message below:

ok: got activation 55b2045f16d84939b2045f16d80939f7
{
    "namespace": "guest",
    "name": "helloPy",
    "version": "0.0.1",
    "subject": "guest",
    "activationId": "55b2045f16d84939b2045f16d80939f7",
    "start": 1629303055599,
    "end": 1629303055599,
    "duration": 0,
    "statusCode": 3,
    "response": {
        "status": "whisk internal error",
        "statusCode": 0,
        "success": false,
        "result": {
            "error": "Failed to provision resources to run the action."
        }
    },
    "logs": [],
    "annotations": [
        {
            "key": "path",
            "value": "guest/helloPy"
        },
        {
            "key": "waitTime",
            "value": 600182
        },
        {
            "key": "kind",
            "value": "python:3"
        },
        {
            "key": "timeout",
            "value": false
        },
        {
            "key": "limits",
            "value": {
                "concurrency": 1,
                "logs": 10,
                "memory": 256,
                "timeout": 60000
            }
        }
    ],
    "publish": false
}

[liusy58]

What's wrong with me?

The procedure is below:

cd tools/ubuntu-tool & ./all.sh

cd -

./gradlew :core:standalone:build

java -jar bin/openwhisk-stanalone.jar

[rabbah]

This error means the docker image for running the action either was not found locally or the container could not be started. Since you're using the standalone openwhisk, and a python action, this image is not pulled automatically on startup. It could be that it took too long for the docker image to be pulled.

The standalone openwhisk emits the logs to the console. Check for an ERROR in the logs related to the activation id and if that doesn't give you a clue please share those logs so we can help. You might also want to use the dev flag shown below if you have the images locally built instead.

      --dev-mode                      Developer mode speeds up the startup by
                                      disabling preflight checks and avoiding
                                      explicit pulls.