Ansible Error: “[Errno 2] No such file or directory”

2
votes

I'm not able to execute kubectl(v1.16.3) commands in the ansible command module.

For e.g. Creation of Namespace using ansible.

    tasks:
       - name: "Creating Directory"
         file:
           path: ~/ansible_ns/demo_namespaces
           state: directory

       - name: "Creating Namespaces(1/2)"
         copy:
           content: "apiVersion: v1 \nkind: Namespace \nmetadata: \n     name: {{item}} "
           dest: "~/ansible_ns/demo_namespaces/{{item}}.yml"
         with_items:
           - "{{ namespace }}"

       - name: "Creating Namespaces(2/2)"
         command: "kubectl create -f {{item}}.yml --kubeconfig=/var/lib/kubernetes/kubeconfig.yaml"
         args:
           chdir: ~/ansible_ns/demo_namespaces/
         ignore_errors: true
         with_items:
           - "{{ namespace }}"

I'm ending up with the below error:

(item=ns) => {
    "ansible_loop_var": "item",
    "changed": false,
    "cmd": "kubectl create -f ns.yml --kubeconfig=/var/lib/kubernetes/kubeconfig.yaml",
    "invocation": {
        "module_args": {
            "_raw_params": "kubectl create -f ns.yml --kubeconfig=/var/lib/kubernetes/kubeconfig.yaml",
            "_uses_shell": false,
            "argv": null,
            "chdir": "/root/ansible_ns/demo_namespaces/",
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": true
        }
    },
    "item": "ns",
    "msg": "[Errno 2] No such file or directory",
    "rc": 2
}

NOTE: But I'm able to do "kubectl create -f .." manually..and it is creating the stuff.

My Ansible version:

$ ansible --version
ansible 2.9.2
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/mdupaguntla/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Aug  4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]

FYI, I also tried with Ansible - 2.4.2 as well. But No luck.

My System OS: CentOS 7

My queries:

  1. What is this error mean "[Errno 2] No such file or directory" in my context?

  2. I came to know that Ansible introduced kubectl & k8s module: Is there anyone in the community using these.. If Yes, please let me know how to use them. If they any prerequisites - please share them For kubectl Module: Came to know that the pre-requisite is kubectl go library.May I know where can I get this Library.

  3. when the kubectl version is 1.8 and ansible version is 2.4.2 - I'm able to get the K8s resources created using "kubectl create -f ..." using command module. But when I upgraded my cluster from v1.8 to v1.16.3 - I'm not able to create the resources using "kubectl create -f ..." using command module. Let me if I missed doing things.

Thanks in advance for the Community

3
kubernetesansible
provide the path for kubectl before the command or try using the shell command or try to give become: true – Smily
1. If I use shell module. I'm getting "/bin/sh: kubectl: command not found". 2. I have already used below things become: true become_method: sudo become_user: root 3. "provide the path for kubectl before the command" - like? - any example? – manoj kumar
I mean path for kubectl. command: "/the/path/kubectl create -f {{item}}.yml. the path where kubectl exists – Smily
@smily - it's working.. thanks a lot... But why I should I place the path of kubectl in the command. Is there any workaround for that? – manoj kumar

3 Answers

3
votes

You have to add the path for kubectl in the command module.

command: "/the/path/kubectl create -f {{item}}.yml .........."

This is because the $PATH is not updated with the path of kubectl. You can add the path to $PATH also instead of giving the path in command module.

0
votes

If you use ansible 2.9.2, it has k8s module available. It provides fully declarative approach ( versus issuing imperative commands ) which is more similar to what you can find in kubernetes itself.

For example if you want to create a new namespace, just use:

- name: Create a k8s namespace
  k8s:
    name: testing
    api_version: v1
    kind: Namespace
    state: present

You have to admit it looks much simpler.

0
votes

Well, there are two ways to make this process better and functional.

You can try to use k8s module like this way.

- name: Create k8s catota namespace
  k8s:
    name: catota
    api_version: v1
    kind: Namespace
    state: present

Or you can use the shell module as well:

- name: Create k8s catota namespace
  shell: "kubectl create namespace catota"
  args:
    executable: /bin/bash