devbox
Monodyee
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

ansible进阶-剧本调试方法

作者：Monodyee | 2024-04-23 16:33:30

赞

踩

ansible进阶-剧本调试方法

目录

1、调试方法

2、实例

2.1    Debug模块

 2.2    tags标签

2.3    忽略错误

1、调试方法

具体方法应用场景
debug标签执⾏剧本的时候输出剧本的执⾏流程,⼀般配合register⼀起使⽤. 输出facts变量自定义变量
tags标签给⼀些模块加上标签,运⾏剧本的时候可以运⾏指定标签的内容,排除指定标签.
忽略错误运⾏剧本的时候忽略⼀些模块的错误,让剧本继续运⾏.

2、实例

2.1    Debug模块
debug
msg相当于是echo命令，配置着register一起用

实例1-调试-nfs服务端部署剧本

剧本文件及执行结果：

  1. [root@ansible ~]# cat debug-nfs-server.yml 
  2. ---
  3. - name: 调试nfs服务端
  4.   hosts: all
  5.   tasks:
  6.     - name: 部署nfs服务端软件
  7.       yum:
  8.         name: nfs-utils
  9.         state: installed 
  10.  
  11.     - name: 创建对应的目录，权限
  12.       file:
  13.         path: /nfsfile
  14.         owner: nfsnobody
  15.         group: nfsnobody
  16.         state: directory
  17.         register: file_jieguo
  18.  
  19.    
  20.     - name: 修改配置文件
  21.       lineinfile: 
  22.         path: /etc/exports
  23.         line: "/nfsfile 192.168.81.0/24(rw,sync,root_squash)"
  24.         state: present
  25.         backup: yes
  26.     
  27.     - name: 输出这个过程
  28.       debug:
  29.         msg: "{{ file_jieguo }}"
  30.  
  31.  
  32.     - name: 启动rpc服务
  33.       systemd:
  34.         name: rpcbind
  35.         enabled: yes
  36.         state: started
  37.  
  38.     - name: 启动nfs服务
  39.       systemd:
  40.         name: nfs
  41.         enabled: yes
  42.         state: started 
  43. [root@ansible ~]# ansible-playbook debug-nfs-server.yml 
  44.  
  45. PLAY [调试nfs服务端] *****************************************************************************************************************************************
  46.  
  47. TASK [Gathering Facts] **********************************************************************************************************************************
  48. ok: [192.168.81.134]
  49. ok: [192.168.81.136]
  50. ok: [192.168.81.133]
  51. ok: [192.168.81.135]
  52. ok: [192.168.81.132]
  53.  
  54. TASK [部署nfs服务端软件] ***************************************************************************************************************************************
  55. ok: [192.168.81.132]
  56. ok: [192.168.81.136]
  57. ok: [192.168.81.133]
  58. ok: [192.168.81.134]
  59. ok: [192.168.81.135]
  60.  
  61. TASK [创建对应的目录，权限] ***************************************************************************************************************************************
  62. changed: [192.168.81.132]
  63. changed: [192.168.81.135]
  64. changed: [192.168.81.136]
  65. changed: [192.168.81.133]
  66. changed: [192.168.81.134]
  67.  
  68. TASK [修改配置文件] *******************************************************************************************************************************************
  69. changed: [192.168.81.132]
  70. changed: [192.168.81.135]
  71. changed: [192.168.81.136]
  72. changed: [192.168.81.134]
  73. changed: [192.168.81.133]
  74.  
  75. TASK [输出这个过程] *******************************************************************************************************************************************
  76. ok: [192.168.81.136] => {
  77.     "msg": {
  78.         "changed": true, 
  79.         "diff": {
  80.             "after": {
  81.                 "group": 65534, 
  82.                 "mode": "0777", 
  83.                 "owner": 65534, 
  84.                 "path": "/nfsfile", 
  85.                 "state": "directory"
  86.             }, 
  87.             "before": {
  88.                 "group": 0, 
  89.                 "mode": "0755", 
  90.                 "owner": 0, 
  91.                 "path": "/nfsfile", 
  92.                 "state": "absent"
  93.             }
  94.         }, 
  95.         "failed": false, 
  96.         "gid": 65534, 
  97.         "group": "nfsnobody", 
  98.         "mode": "0777", 
  99.         "owner": "nfsnobody", 
  100.         "path": "/nfsfile", 
  101.         "secontext": "unconfined_u:object_r:default_t:s0", 
  102.         "size": 6, 
  103.         "state": "directory", 
  104.         "uid": 65534
  105.     }
  106. }
  107. ok: [192.168.81.132] => {
  108.     "msg": {
  109.         "changed": true, 
  110.         "diff": {
  111.             "after": {
  112.                 "group": 65534, 
  113.                 "mode": "0777", 
  114.                 "owner": 65534, 
  115.                 "path": "/nfsfile", 
  116.                 "state": "directory"
  117.             }, 
  118.             "before": {
  119.                 "group": 0, 
  120.                 "mode": "0755", 
  121.                 "owner": 0, 
  122.                 "path": "/nfsfile", 
  123.                 "state": "absent"
  124.             }
  125.         }, 
  126.         "failed": false, 
  127.         "gid": 65534, 
  128.         "group": "nfsnobody", 
  129.         "mode": "0777", 
  130.         "owner": "nfsnobody", 
  131.         "path": "/nfsfile", 
  132.         "secontext": "unconfined_u:object_r:default_t:s0", 
  133.         "size": 6, 
  134.         "state": "directory", 
  135.         "uid": 65534
  136.     }
  137. }
  138. ok: [192.168.81.134] => {
  139.     "msg": {
  140.         "changed": true, 
  141.         "diff": {
  142.             "after": {
  143.                 "group": 65534, 
  144.                 "mode": "0777", 
  145.                 "owner": 65534, 
  146.                 "path": "/nfsfile", 
  147.                 "state": "directory"
  148.             }, 
  149.             "before": {
  150.                 "group": 0, 
  151.                 "mode": "0755", 
  152.                 "owner": 0, 
  153.                 "path": "/nfsfile", 
  154.                 "state": "absent"
  155.             }
  156.         }, 
  157.         "failed": false, 
  158.         "gid": 65534, 
  159.         "group": "nfsnobody", 
  160.         "mode": "0777", 
  161.         "owner": "nfsnobody", 
  162.         "path": "/nfsfile", 
  163.         "secontext": "unconfined_u:object_r:default_t:s0", 
  164.         "size": 6, 
  165.         "state": "directory", 
  166.         "uid": 65534
  167.     }
  168. }
  169. ok: [192.168.81.133] => {
  170.     "msg": {
  171.         "changed": true, 
  172.         "diff": {
  173.             "after": {
  174.                 "group": 65534, 
  175.                 "mode": "0777", 
  176.                 "owner": 65534, 
  177.                 "path": "/nfsfile", 
  178.                 "state": "directory"
  179.             }, 
  180.             "before": {
  181.                 "group": 0, 
  182.                 "mode": "0755", 
  183.                 "owner": 0, 
  184.                 "path": "/nfsfile", 
  185.                 "state": "absent"
  186.             }
  187.         }, 
  188.         "failed": false, 
  189.         "gid": 65534, 
  190.         "group": "nfsnobody", 
  191.         "mode": "0777", 
  192.         "owner": "nfsnobody", 
  193.         "path": "/nfsfile", 
  194.         "secontext": "unconfined_u:object_r:default_t:s0", 
  195.         "size": 6, 
  196.         "state": "directory", 
  197.         "uid": 65534
  198.     }
  199. }
  200. ok: [192.168.81.135] => {
  201.     "msg": {
  202.         "changed": true, 
  203.         "diff": {
  204.             "after": {
  205.                 "group": 65534, 
  206.                 "mode": "0777", 
  207.                 "owner": 65534, 
  208.                 "path": "/nfsfile", 
  209.                 "state": "directory"
  210.             }, 
  211.             "before": {
  212.                 "group": 0, 
  213.                 "mode": "0755", 
  214.                 "owner": 0, 
  215.                 "path": "/nfsfile", 
  216.                 "state": "absent"
  217.             }
  218.         }, 
  219.         "failed": false, 
  220.         "gid": 65534, 
  221.         "group": "nfsnobody", 
  222.         "mode": "0777", 
  223.         "owner": "nfsnobody", 
  224.         "path": "/nfsfile", 
  225.         "secontext": "unconfined_u:object_r:default_t:s0", 
  226.         "size": 6, 
  227.         "state": "directory", 
  228.         "uid": 65534
  229.     }
  230. }
  231.  
  232. TASK [启动rpc服务] ******************************************************************************************************************************************
  233. changed: [192.168.81.134]
  234. changed: [192.168.81.133]
  235. changed: [192.168.81.132]
  236. changed: [192.168.81.135]
  237. changed: [192.168.81.136]
  238.  
  239. TASK [启动nfs服务] ******************************************************************************************************************************************
  240. changed: [192.168.81.136]
  241. changed: [192.168.81.133]
  242. changed: [192.168.81.134]
  243. changed: [192.168.81.132]
  244. changed: [192.168.81.135]
  245.  
  246. PLAY RECAP **********************************************************************************************************************************************
  247. 192.168.81.132             : ok=7    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
  248. 192.168.81.133             : ok=7    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
  249. 192.168.81.134             : ok=7    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
  250. 192.168.81.135             : ok=7    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
  251. 192.168.81.136             : ok=7    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
  252.  
  253. [root@ansible ~]#

 2.2    tags标签

Ansible中的tags标签用于为任务指定标记，并在运行时根据指定的标记只运行部分任务，从而避免对整个剧本进行执行。在编写包含多个任务的剧本时，有时候只需要在执行时运行其中一任务。这时，使用tag标签是非常有用的，它可以为每个任务指定一个标签，这样在执行时只需要运行指定标签的任务即可。

也可以这样理解

一个剧本里面可能包涵了多个任务，但是又不知道剧本中任务是不是都能执行，不确定，这个时候就可以用标签标记任务，然后运行剧本时指定标签运行不确定能不能执行的任务

执行剧本时，使用--tags选项指定要运行的标签。

运行指定的标签

ansible-play --tags 自定义的标签名 剧本文件名

运行剧本的时候排除指定的标签

ansible-play --skip-tags 要排除的标签名 剧本文件名

实例

2.3    忽略错误

当运行剧本时，剧本是按照任务的编写顺序执行，当某个任务运行出现错误时，则则这个任务下面的任务出现错误时，

用于运行剧本的时候，强制让某个任务（模块）运行即使出现错误，也不会中断我们整个剧本的执行。

实例

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/Monodyee/article/detail/474924
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号