Another quick blog which will save your time in order to fight with quotes and braces while writing ansible. This piece of code allows you to put curly braces, quotes, and necessary quotes via evil-surround Call evil-surround-edit command and press h converts item ==> {{ item }} H […]
Note after long time: The reason that I used that technique was using for implementation in Cloudformation but after time I realized that solution is getting hard to maintain. Solution is easy and still usable but after that time I recommend to use Terraform for same action. Why we have […]
This is a fast time saver blog post that shows how to get value of nested variable which has dynamic part in Ansible Jinja2 template For More: https://serverfault.com/questions/762079/how-to-loop-through-interface-facts https://github.com/pallets/jinja/issues/623 https://stackoverflow.com/questions/10894693/jinja2-nested-variables
It looks like really general problem. Fast blog which solve problem about creating molecule role Error log
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 |
➜ trozgene@macbook-pro-2 ~/Githubdosyalari/ansible/roles git:(master) molecule init --role create-S3-stack --driver docker 11:13:23 --> Initializing role create-S3-stack... Traceback (most recent call last): File "/usr/local/bin/molecule", line 11, in <module> sys.exit(main()) File "/Library/Python/2.7/site-packages/molecule/cli.py", line 41, in main cli(obj={}) File "/Library/Python/2.7/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/Library/Python/2.7/site-packages/click/core.py", line 697, in main rv = self.invoke(ctx) File "/Library/Python/2.7/site-packages/click/core.py", line 1066, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/Library/Python/2.7/site-packages/click/core.py", line 895, in invoke return ctx.invoke(self.callback, **ctx.params) File "/Library/Python/2.7/site-packages/click/core.py", line 535, in invoke return callback(*args, **kwargs) File "/Library/Python/2.7/site-packages/click/decorators.py", line 17, in new_func return f(get_current_context(), *args, **kwargs) File "/Library/Python/2.7/site-packages/molecule/command/init.py", line 141, in init util.sysexit(i.execute()[0]) File "/Library/Python/2.7/site-packages/molecule/command/init.py", line 60, in execute self._init_new_role(role, role_path, driver, verifier) File "/Library/Python/2.7/site-packages/molecule/command/init.py", line 85, in _init_new_role util.process_templates(template, extra_context, role_path) File "/Library/Python/2.7/site-packages/molecule/util.py", line 115, in process_templates no_input=True, ) File "/Library/Python/2.7/site-packages/cookiecutter/main.py", line 82, in cookiecutter context['cookiecutter'] = prompt_for_config(context, no_input) File "/Library/Python/2.7/site-packages/cookiecutter/prompt.py", line 188, in prompt_for_config env = StrictEnvironment(context=context) File "/Library/Python/2.7/site-packages/cookiecutter/environment.py", line 70, in __init__ **kwargs File "/Library/Python/2.7/site-packages/cookiecutter/environment.py", line 40, in __init__ raise UnknownExtension('Unable to load extension: {}'.format(err)) cookiecutter.exceptions.UnknownExtension: Unable to load extension: cannot import name _thread |
Solution
|
1 2 |
sudo pip uninstall python-dateutil sudo pip install python-dateutil==2.2 |
Reference https://stackoverflow.com/questions/27630114/matplotlib-issue-on-os-x-importerror-cannot-import-name-thread
Edit: 1.1.2019. Few days ago I learned how to use test command. I think that can be solve faster defined problem. Related link Usefull small ansible script that checks is program exist
Ansible-playbooks has own output style. In this blog post I have just shared YAML file that explains how to handle return codes in ansible-playbooks So there is an example that handles errors of Ansible.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
- hosts: localhost gather_facts: no #strategy: debug tasks: - name: run this command and ignore the result shell: ping -c 1 8.8.8.8 register: pingout ignore_errors: yes - debug: msg="{{ pingout.rc }}" - name: Prepare well output raw: echo "What a wonderful world" register: output when: pingout.rc == 0 - debug: var=output - name: run this command and ignore the result raw: ping -c 1 8.8.8.7 register: pingout2 ignore_errors: yes - debug: msg="{{ pingout2.rc }}" - name: run this command if something wrong shell: echo "Something goes wrong :)" register: output2 when: pingout2.rc != 0 - debug: var=output2 |
Output:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
PLAY [localhost] *************************************************************** TASK [run this command and ignore the result] ********************************** changed: [127.0.0.1] TASK [debug] ******************************************************************* ok: [127.0.0.1] => { "msg": "0" } TASK [run this command if everything is okey] ********************************** changed: [127.0.0.1] TASK [debug] ******************************************************************* ok: [127.0.0.1] => { "output": { "changed": true, "cmd": "echo \"What a wonderful world\"", "delta": "0:00:00.001372", "end": "2016-08-18 11:16:11.745843", "rc": 0, "start": "2016-08-18 11:16:11.744471", "stderr": "", "stdout": "What a wonderful world", "stdout_lines": [ "What a wonderful world" ], "warnings": [] } } TASK [run this command and ignore the result] ********************************** fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "rc": 1, "stderr": "", "stdout": "PING 8.8.8.7 (8.8.8.7) 56(84) bytes of data.\r\n\r\n--- 8.8.8.7 ping statistics ---\r\n1 packets transmitted, 0 received, 100% packet loss, time 0ms\r\n\r\n", "stdout_lines": ["PING 8.8.8.7 (8.8.8.7) 56(84) bytes of data.", "", "--- 8.8.8.7 ping statistics ---", "1 packets transmitted, 0 received, 100% packet loss, time 0ms", ""]} ...ignoring TASK [debug] ******************************************************************* ok: [127.0.0.1] => { "msg": "1" } TASK [run this command if something wrong] ************************************* ok: [127.0.0.1] TASK [debug] ******************************************************************* ok: [127.0.0.1] => { "output2": { "changed": false, "rc": 0, "stderr": "", "stdout": "Something goes wrong :)\r\n", "stdout_lines": [ "Something goes wrong :)" ] } } PLAY RECAP ********************************************************************* 127.0.0.1 : ok=8 changed=2 unreachable=0 failed=0 |
That playbook will not return with failed status because of that we […]
vsphere_guest really efficient tool while working VMware. It has many many feature to boot machine by using Ansible. While working with it I think there is good examples to understand how it works but in my opinion nobody has time to try and work with all examples with all different […]
