In some situations, you may encounter an error like this in the Ansible output when you're trying to perform a new installation of DKP 1.X:
TASK [kubeadm-control-plane : get all pod IDs] *******************************************************************************************************************************************************************************************************************************
[0;31mfatal: [10.1.0.5]: FAILED! => {[0m
[0;31m "ansible_facts": {[0m
[0;31m "discovered_interpreter_python": "/usr/bin/python"[0m
[0;31m },[0m
[0;31m "changed": false,[0m
[0;31m "cmd": "crictl pods -q", [0m
[0;31m "rc": 2[0m
[0;31m}[0m
[0;31m[0m
[0;31mMSG:[0m
[0;31m[0m
[0;31m[Errno 2] No such file or directory [0m
This often indicates a version mismatch between the configuration file you're using and the binary that you're running.
If you encounter this issue, please make sure that you are using a config.yaml version that matches the 'konvoy' binary that you are using,
and that you are actually running the proper "./konvoy" command in the correct working directory, not one in your $PATH.
To check the version of the 'konvoy' binary, you can run:
./konvoy --version
To check to make sure your cluster.yaml matches the appropriate binary version, you can first check these two fields:
kind: ClusterProvisioner
apiVersion: konvoy.mesosphere.io/v1beta2
metadata:
name: konvoy_v1.8.3
...
kind: ClusterConfiguration
apiVersion: konvoy.mesosphere.io/v1beta2
metadata:
name: konvoy_v1.8.3
Then, you can check the Kubernetes and Kubernetes Base Addons versions:
spec:
kubernetes:
version: 1.20.11
...
addons:
- configRepository: https://github.com/mesosphere/kubernetes-base-addons
configVersion: stable-1.20-4.2.0
Compare the version here to the Kubernetes and KBA versions in the release notes for the appropriate Konvoy version. For instance, for Konvoy 1.8.3:
If you're having a version mismatch problem and are unsure how to resolve it, please file a ticket with our support team: