ansible-elastic-cloud-enterprise icon indicating copy to clipboard operation
ansible-elastic-cloud-enterprise copied to clipboard

Idempotence issue? Errors are "No filter named 'from_json'", then "Container frc-directors-director was not found"

Open chuckmilam opened this issue 1 year ago • 0 comments

Current environment: Running against three CentOS Stream 8 AMIs. Using Ansbile 2.8.7 in a fresh python venv.

First run of the small playbook as described in the README gives this error:

 fatal: [xxx.xxx.xxx.xxx]: FAILED! => {
     "msg": "template error while templating string: No filter named 'from_json'.. String: {{ secrets.stdout|from_json }}"
 }

When running a second time, we get this error:

fatal: [xxx.xxx.xxx.xxx]: FAILED! => {
    "changed": true,
    "cmd": "/home/elastic/elastic-cloud-enterprise.sh upgrade --cloud-enterprise-version 3.5.1 --docker-registry docker.elastic.co --ece-docker-repository cloud-enterprise",
    "delta": "0:00:00.597917",
    "end": "2023-06-20 14:34:56.284261",
    "invocation": {
        "module_args": {
            "_raw_params": "/home/elastic/elastic-cloud-enterprise.sh upgrade --cloud-enterprise-version 3.5.1 --docker-registry docker.elastic.co --ece-docker-repository cloud-enterprise",
            "_uses_shell": true,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": true
        }
    },
    "msg": "non-zero return code",
    "rc": 1,
    "start": "2023-06-20 14:34:55.686344",
    "stderr": "",
    "stderr_lines": [],
    "stdout": "\u001b[0;31mContainer frc-directors-director was not found -- does the current host have a role 'director'?\u001b[0m",
    "stdout_lines": [
        "\u001b[0;31mContainer frc-directors-director was not found -- does the current host have a role 'director'?\u001b[0m"
    ]
}

If I log directly into the primary node and do a docker ps -a, the "frc-directors-director" container is present and healthy.

Running the playbook again errors out at the same "Container frc-directors-director was not found" point.

chuckmilam avatar Jun 20 '23 16:06 chuckmilam