如何在Ansible中为多主机分配IP并规避重复报错？

我需要给不同主机分配一段IP地址，但必须先检查目标IP是否已被占用。目前通过ignore_errors: yes跳过IP已存在的报错，但希望找到更优雅的解决方案。

现有剧本 #

---
- hosts: all
  gather_facts: yes
  become: yes
  vars_files:
   - client2
  tasks:
   - set_fact:
       intip: "{{ intip | default([]) + [item] }}"
     loop: "{{ ansible_interfaces | map('extract',ansible_facts, 'ipv4') | select('defined') | map(attribute='address') | list }}"
     ignore_errors: yes
   - name: Check IP address
     shell:
       "ip a a '{{ start_ip|ipmath(my_idx) }}' dev spanbr"
     loop_control:
      index_var: my_idx
     when: (item == inventory_hostname )
     loop: "{{ ansible_play_hosts }}"
     ignore_errors: yes

变量文件 #

待尝试的变量文件（未验证） #

client:
  - interface:
    - local_ip: 10.10.10.10
    - name: eth1 
  - interface:
    - local_ip: 10.10.10.11
    - name: eth1 

当前使用的变量文件 #

interface:
  - config:
    - name: eth0 
  - config:
    - name: eth1

start_ip: 10.10.10.10

当前执行输出 #

Output:
TASK [Check IP address] ************************************************************************************************************************
skipping: [host2] => (item=host1)
failed: [host1] (item=host1) => {"ansible_index_var": "my_idx", "ansible_loop_var": "item", "changed": true, "cmd": "ip a a '10.10.10.10' dev spanbr", "delta": "0:00:00.005429", "end": "2022-10-20 08:49:43.800954", "item": "host1", "msg": "non-zero return code", "my_idx": 0, "rc": 2, "start": "2022-10-20 08:49:43.795525", "stderr": "RTNETLINK answers: File exists", "stderr_lines": ["RTNETLINK answers: File exists"], "stdout": "", "stdout_lines": []}
skipping: [host1] => (item=host2)
...ignoring
failed: [host2] (item=host2) => {"ansible_index_var": "my_idx", "ansible_loop_var": "item", "changed": true, "cmd": "ip a a '10.10.10.11' dev spanbr", "delta": "0:00:00.002691", "end": "2022-10-20 07:49:43.815422", "item": "host2", "msg": "non-zero return code", "my_idx": 1, "rc": 2, "start": "2022-10-20 07:49:43.812731", "stderr": "RTNETLINK answers: File exists", "stderr_lines": ["RTNETLINK answers: File exists"], "stdout": "", "stdout_lines": []}
...ignoring

intip变量输出参考 #

TASK [set_fact] ********************************************************************************************************************************
ok: [host1] => (item=192.168.1.100)
ok: [host1] => (item=127.0.0.1)
ok: [host1] => (item=10.10.10.10)
ok: [host1] => (item=169.254.0.1)
ok: [host2] => (item=127.0.0.1)
ok: [host2] => (item=10.10.10.11)
ok: [host2] => (item=192.168.1.101)

解决方案思路 #

1. 提前检查IP状态，避免执行报错 #

利用已收集的intip变量（或Ansible内置的ansible_all_ipv4_addresses）提前判断目标IP是否存在，仅在IP未被占用时执行分配操作，完全不需要ignore_errors：

- name: 计算当前主机的目标IP
  set_fact:
    target_ip: "{{ start_ip | ipmath(ansible_play_hosts.index(inventory_hostname)) }}"

- name: 分配IP（仅当IP未存在时）
  shell: "ip a a '{{ target_ip }}' dev spanbr"
  when: target_ip not in intip

如果需要更严谨的跨主机IP冲突检查，可以收集所有主机的IP到全局变量后再判断：

- name: 收集所有主机的IP地址
  set_fact:
    all_host_ips: "{{ all_host_ips | default([]) + intip }}"
  delegate_to: localhost
  run_once: true

- name: 分配IP（无跨主机冲突且本地未占用）
  shell: "ip a a '{{ target_ip }}' dev spanbr"
  when: 
    - target_ip not in intip
    - target_ip not in all_host_ips

2. 优化变量结构，提升可维护性 #

放弃当前扁平变量结构，改用主机-IP-接口的映射关系，配置更清晰且适配所有主机：

# 优化后的变量文件（client2.yml）
host_network_configs:
  host1:
    target_interface: spanbr
    target_ip: 10.10.10.10
  host2:
    target_interface: spanbr
    target_ip: 10.10.10.11

对应的任务可简化为：

- name: 分配IP（仅当IP未存在时）
  shell: "ip a a '{{ host_network_configs[inventory_hostname].target_ip }}' dev {{ host_network_configs[inventory_hostname].target_interface }}"
  when: host_network_configs[inventory_hostname].target_ip not in intip

如果需要自动按段分配IP，保留start_ip并通过主机索引计算更简洁：

# 变量文件
start_ip: 10.10.10.10
target_interface: spanbr

任务部分：

- name: 计算目标IP
  set_fact:
    target_ip: "{{ start_ip | ipmath(ansible_play_hosts.index(inventory_hostname)) }}"

- name: 分配IP
  shell: "ip a a '{{ target_ip }}' dev {{ target_interface }}"
  when: target_ip not in intip

3. 简化循环逻辑，提升执行效率 #

原任务通过循环所有主机再用when过滤当前主机属于无效循环。直接针对当前主机计算目标IP，避免不必要的循环操作，减少执行时间和日志冗余。

内容的提问来源于stack exchange，提问作者Junk