blocks|key|2527524|text|已更新答案|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2527525|我认为你需要在它周围加上引号：|2527526|register:+"{{+item+}}_service_status"|code-block|syntax|javascript|2527527|也可以使用set_fact+(1、2、3、4)|CODE|2527528|通过循环静态变量output中的每一项，|2527529|将所有输出注册到单个静态变量output，然后使用循环迭代地构建新的变量service_status+(list|unordered-list-item|2527530|2527531|-+name:+Check+if+Service+Exists
++stat:+path=/etc/init.d/{{+item+}}
++register:+output
++with_items:
+++++-+XXX
+++++-+YYY
+++++-+ZZZ

-+name:+Setting+fact+using+output+of+loop
++set_fact:
++++service_status:
++++++-+rc:+"{{+item.rc+}}"
++++++++stdout:+"{{+item.stdout+}}"
++++++++id:+"{{+item.id+}}"
++with_items:
++++-+"{{+output+}}"

-+debug:
++++msg:+"ID+and+stdout:+{{+item.id+}}+-+{{+item.stdout+}}"
++with_items:
++++-+"{{+service_status+}}"|2527532|2527533|初始答案|2527534|Ansible文档中的this+link展示了如何在循环中使用register+(参见this+SO+post中的另一个示例)。|2527535|有几点|2527536|2527537|将列表(XXX,+YYY,+ZZZ)分配给单独的变量可能更方便(例如，2)|2527538|I，1不知道这是否是问题的一部分，但是with_items+is+no+longer+the+recommended+approach循环遍历变量:而不是使用loop+-参见here以获取|2527539|的示例|2527540|vars:
++items:
++++-+XXX
++++-+YYY
++++-+ZZZ

-+name:+Check+if+Service+Exists
++stat:+path=/etc/init.d/{{+item+}}
++register:+service_status
++loop:+"{{+items%7Cflatten(levels=1)+}}"

-+name:+Show+the+return+code+and+stdout
++debug:
++++msg:+"Cmd+{{+item.cmd+}},+return+code+{{+item.rc+}},+stdout+{{+item.stdout+}}"
++when:+item.rc+!=+0
++with_items:+"{{+service_status.results+}}"|2527541|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/44073969/4057186|1|https://unix.stackexchange.com/a/208860/255869|2|https://stackoverflow.com/a/29817564/4057186|3|https://stackoverflow.com/a/43633611/4057186|4|https://everythingshouldbevirtual.com/automation/ansible-defining-variables-as-dictionaries/|5|https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#using-register-with-a-loop|6|https://stackoverflow.com/a/29636407/4057186|7|http://www.oznetnerd.com/ansible-vars-lists/|8|http://www.mydailytutorials.com/the-basics-of-ansible-variables/|9|https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#migrating-from-with-x-to-loop|10|https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#with-items^0|0|5|0|0|0|5|8|F|1|0|H|1|1|J|1|2|L|1|3|0|8|6|0|E|6|10|E|1G|4|4|0|0|0|0|0|4|0|V|8|B|9|5|17|C|6|0|0|0|4|D|Z|1|7|0|J|A|27|4|2|1|8|U|11|9|2F|4|A|0|0|0^^$0|@$1|2|3|4|5|6|7|25|8|@$9|26|A|27|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|28|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|29|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|2A|8|@$9|2B|A|2C|B|O]]|D|@$9|2D|A|2E|1|2F]|$9|2G|A|2H|1|2I]|$9|2J|A|2K|1|2L]|$9|2M|A|2N|1|2O]]|E|$]]|$1|P|3|Q|5|6|7|2P|8|@$9|2Q|A|2R|B|O]]|D|@]|E|$]]|$1|R|3|S|5|T|7|2S|8|@$9|2T|A|2U|B|O]|$9|2V|A|2W|B|O]]|D|@$9|2X|A|2Y|1|2Z]]|E|$]]|$1|U|3|-4|5|6|7|30|8|@]|D|@]|E|$]]|$1|V|3|W|5|J|7|31|8|@]|D|@]|E|$K|L]]|$1|X|3|-4|5|6|7|32|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|33|8|@$9|34|A|35|B|C]]|D|@]|E|$]]|$1|10|3|11|5|6|7|36|8|@$9|37|A|38|B|O]]|D|@$9|39|A|3A|1|3B]|$9|3C|A|3D|1|3E]]|E|$]]|$1|12|3|13|5|6|7|3F|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|3G|8|@]|D|@]|E|$]]|$1|15|3|16|5|T|7|3H|8|@$9|3I|A|3J|B|O]]|D|@$9|3K|A|3L|1|3M]]|E|$]]|$1|17|3|18|5|T|7|3N|8|@$9|3O|A|3P|B|O]|$9|3Q|A|3R|B|O]]|D|@$9|3S|A|3T|1|3U]|$9|3V|A|3W|1|3X]|$9|3Y|A|3Z|1|40]]|E|$]]|$1|19|3|1A|5|6|7|41|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|J|7|42|8|@]|D|@]|E|$K|L]]|$1|1D|3|-4|5|6|7|43|8|@]|D|@]|E|$]]]|1E|$1F|$5|1G|1H|1I|E|$1J|1K]]|1L|$5|1G|1H|1I|E|$1J|1M]]|1N|$5|1G|1H|1I|E|$1J|1O]]|1P|$5|1G|1H|1I|E|$1J|1Q]]|1R|$5|1G|1H|1I|E|$1J|1S]]|1T|$5|1G|1H|1I|E|$1J|1U]]|1V|$5|1G|1H|1I|E|$1J|1W]]|1X|$5|1G|1H|1I|E|$1J|1Y]]|1Z|$5|1G|1H|1I|E|$1J|20]]|21|$5|1G|1H|1I|E|$1J|22]]|23|$5|1G|1H|1I|E|$1J|24]]]]

Updated answer

I think you need to put quotes around it:

<pre><code>register: "{{ item }}_service_status"
</code></pre>

Or you can use <code>set_fact</code> (<a href="https://stackoverflow.com/a/44073969/4057186">1</a>, <a href="https://unix.stackexchange.com/a/208860/255869">2</a>, <a href="https://stackoverflow.com/a/29817564/4057186">3</a>, <a href="https://stackoverflow.com/a/43633611/4057186">4</a>)

<ul>
<li>register all the output to a single static variable <code>output</code> and then use a loop to iteratively build a new variable <code>service_status</code> (a <a href="https://everythingshouldbevirtual.com/automation/ansible-defining-variables-as-dictionaries/" rel="nofollow noreferrer">list</a>) by looping over each item in the static variable <code>output</code></li>
</ul>

<pre><code>- name: Check if Service Exists
 stat: path=/etc/init.d/{{ item }}
 register: output
 with_items:
 - XXX
 - YYY
 - ZZZ

- name: Setting fact using output of loop
 set_fact:
 service_status:
 - rc: "{{ item.rc }}"
 stdout: "{{ item.stdout }}"
 id: "{{ item.id }}"
 with_items:
 - "{{ output }}"

- debug:
 msg: "ID and stdout: {{ item.id }} - {{ item.stdout }}"
 with_items:
 - "{{ service_status }}"
</code></pre>

<hr>

Initial Answer

IIUC, <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#using-register-with-a-loop" rel="nofollow noreferrer">this link</a> from the Ansible docs shows how to use <code>register</code> inside a loop (see another example in <a href="https://stackoverflow.com/a/29636407/4057186">this SO post</a>).

A couple of points

<ul>
<li>it may be more convenient to assign the list (<code>XXX, YYY, ZZZ</code>) to a separate variable (eg. <a href="http://www.mydailytutorials.com/the-basics-of-ansible-variables/" rel="nofollow noreferrer">1</a>, <a href="http://www.oznetnerd.com/ansible-vars-lists/" rel="nofollow noreferrer">2</a>)</li>
<li>I don't know if this is part of the problem, but <code>with_items</code> <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#migrating-from-with-x-to-loop" rel="nofollow noreferrer">is no longer the recommended approach</a> to loop over a variable: instead use <code>loop</code> - see <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#with-items" rel="nofollow noreferrer">here</a> for an example</li>
</ul>

<pre><code>vars:
 items:
 - XXX
 - YYY
 - ZZZ

- name: Check if Service Exists
 stat: path=/etc/init.d/{{ item }}
 register: service_status
 loop: "{{ items|flatten(levels=1) }}"

- name: Show the return code and stdout
 debug:
 msg: "Cmd {{ item.cmd }}, return code {{ item.rc }}, stdout {{ item.stdout }}"
 when: item.rc != 0
 with_items: "{{ service_status.results }}"
</code></pre>

I am trying to use a register in Ansible playbook to store my output. Below is the code which i am using. 

I have tried below code

<pre><code>- name: Check if Service Exists
 stat: path=/etc/init.d/{{ item }}
 register: {{ item }}_service_status
 with_items:
 - XXX
 - YYY
 - ZZZ
</code></pre>

I need different outputs to be stored in different register variables based on the items as mentioned in the code. It is failing and not able to proceed. Any help would be appreciated.

Ansible Registers - Dynamic naming

我正在尝试使用Ansible playbook中的一个寄存器来存储我的输出。下面是我正在使用的代码。我试过下面的代码- name: Check if Service Exists  stat: path=/etc/init.d/{{ item }}  register: {{ item }}_service_statu...

问Ansible寄存器-动态命名
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ansible寄存器-动态命名EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ansible寄存器-动态命名
EN