Run Ansible command failed. epicli:2.0.3 version

[MurugaAzure]

terraform execution done.
Ansible failed.

OS : Linux(Ubuntu 20.04)
Epiphany Version : 2.0.3

2023-01-18T13:00:47.5873418Z 13:00:47 INFO cli.src.ansible.AnsibleCommand - TASK [applications : Include applications] *************************************�[0m
2023-01-18T13:00:47.6635346Z 13:00:47 INFO cli.src.ansible.AnsibleCommand - �[0;31mfatal: [127.0.0.1]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}�[0m�[0m
2023-01-18T13:00:47.6719460Z 13:00:47 INFO cli.src.ansible.AnsibleCommand - �[0m
2023-01-18T13:00:47.7688514Z 13:00:47 INFO cli.src.commands.Apply - Step finished in: 46m 23.05s�[0m
2023-01-18T13:00:47.7690350Z �[31m13:00:47 ERROR epicli - Error running: "ansible-playbook -i /shared/build/prod-mt-gulf-cluster/inventory --vault-password-file /home/epiuser/.epicli/vault.cfg /shared/build/prod-mt-gulf-cluster/ansible/applications.yml"�[0m
2023-01-18T13:00:49.5594005Z 13:00:49 INFO dump_debug_info - Error dump has been written to: /shared/epicli_error_20230118-130047.dump�[0m
2023-01-18T13:00:49.5595331Z �[33m13:00:49 WARNING dump_debug_info - This dump might contain sensitive information. Check before sharing.�[0m
2023-01-18T13:00:49.5635924Z 13:00:49 INFO run_time - Total run time: 46m 24.85s�[0m
2023-01-18T13:00:49.6375499Z ##[error]Bash exited with code '1'.
2023-01-18T13:00:49.6404705Z ##[section]Finishing: Execute the yaml file skipping the infra

[MurugaAzure]

@przemyslavic

I shared error log information. Could you look it?

I need your help to sort out this issue.

[MurugaAzure]

@przemyslavic

Change no_log: false (here)

I need your help.

[przemyslavic]

@MurugaAzure Could you please post your configuration for kind: epiphany-cluster and kind: configuration/applications after removing sensitive data?

[przemyslavic]

It's hard to read 😏
First of all, in the application section you have Keycloak v14 enabled. Keycloak was updated to v19 and is installed in a different way starting from v2.0.2 and it was removed from kind: configuration/applications (link). You also need PostgreSQL component to deploy Keycloak and you have it set to 0. You just applied the wrong configuration.
Please run epicli init -p <provider> -n <name> --full to generate the correct configuration and then adjust it to your needs.

[MurugaAzure]

Thanks @przemyslavic ,

[MurugaAzure]

Hello @przemyslavic,

I used epicli 2.0.3 version. Run Ansible failed.

2023-01-23T10:22:46.9330296Z 10:22:46 INFO cli.src.ansible.AnsibleCommand - TASK [kubernetes_master : Initialize Kubernetes cluster] ***********************�[0m
2023-01-23T10:22:47.5117182Z 10:22:47 INFO cli.src.ansible.AnsibleCommand - �[0;31mfatal: [test-epip-test-cluster-kubernetes-master-vm-0]: FAILED! => {"changed": true, "cmd": "kubeadm init --config /etc/kubeadm/kubeadm-config.yml\n", "delta": "0:00:00.240808", "end": "2023-01-23 10:22:47.467823", "msg": "non-zero return code", "rc": 1, "start": "2023-01-23 10:22:47.227015", "stderr": "error execution phase preflight: [preflight] Some fatal errors occurred:\n\t[ERROR CRI]: container runtime is not running: output: time="2023-01-23T10:22:47Z" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"\n, error: exit status 1\n[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...\nTo see the stack trace of this error execute with --v=5 or higher", "stderr_lines": ["error execution phase preflight: [preflight] Some fatal errors occurred:", "\t[ERROR CRI]: container runtime is not running: output: time="2023-01-23T10:22:47Z" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"", ", error: exit status 1", "[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...", "To see the stack trace of this error execute with --v=5 or higher"], "stdout": "[init] Using Kubernetes version: v1.22.4\n[preflight] Running pre-flight checks", "stdout_lines": ["[init] Using Kubernetes version: v1.22.4", "[preflight] Running pre-flight checks"]}�[0m�[0m

[przemyslavic]

@MurugaAzure are you sure you didn't forget the asterisk? For Ubuntu it should be cri-tools=1.25.0*, not cri-tools=1.25.0
https://github.com/epiphany-platform/epiphany/pull/3314/files#diff-53b66c0008b575c1884d21323a8ea2179f7628543c4ca65348908008300ff1ddR11

root@0678a797ca31:/# apt-cache show cri-tools=1.25.0
E: Version '1.25.0' for 'cri-tools' was not found
E: No packages found

root@0678a797ca31:/# apt-cache show cri-tools=1.25.0*
Package: cri-tools
Version: 1.25.0-00

Nevertheless, today or tomorrow morning we should be releasing 2.0.4.

[MurugaAzure]

Sure @przemyslavic.

i will add cri-tools=1.25.0*

Thank you so much for quick reply.

[przemyslavic]

@MurugaAzure v2.0.4 has just been released ☺️
https://github.com/epiphany-platform/epiphany/releases/tag/v2.0.4

[MurugaAzure]

Thanks @przemyslavic 👍

[MurugaAzure]

Hello @przemyslavic,

I can able to create Infra and provisioning VM cluster.
terraform and Ansible successfully completed without issue.

Thank you so much.