How to handle network changes and restart with Ansible?

inframan

2/20/24, 3:06 PM

I'm currently developping a network configuration role used by Ansible to customize our fresh new virtual machine that came from our Debian 11 template.

The following role changes from DHCP to static interface configuration and then restart the networking service.For testing purpose i set IP/netmask/gateway as extra vars (and it's dynamically changed depends on the server i have to use my role)

  - name: ens3 reconfiguration 
    ansible.builtin.template:
      src: interfaces.j2
      dest: /etc/network/interfaces
 
  - name: Restart  networking.service
    ansible.builtin.service:
      name: networking
      state: restarted

Here's the content of interfaces.j2 for understanding.

# The primary network interface
auto ens3
iface ens3 inet static
  address {{ ens3_ip }}/{{ ens3_netmask }}
  gateway {{ ens3_gateway }}
  dns-nameservers X.X.X.X
  dns-search my_domain.net

The problem here is, as the network interface is dhcp configured, it has for example 10.0.0.1, i reconfigure it with 10.0.0.50, then Ansible move to the restart networking.service task, and gets hang forever...

**From an Ansible perspective, is it possible to dynamically reconnect to the host with the new IP ? or maybe, bypass the execution result of the restart networking.service ? **

1245

1 + 1

networking

linux-networking

template

ansible

ansible-playbook

Peter Zhabin

2/20/24, 4:29 PM

This is really a duplicate for https://stackoverflow.com/questions/60181867/ansible-is-there-a-way-to-change-a-windows-server-ip-address-using-ansible/

Score:1

Server

Illuminatus

2/21/24, 10:04 PM

While very close to the question listed by https://serverfault.com/users/378597/peter-zhabin uses win_shell, which is not applicable to Linux.

Off the top of my head it seems like this would be the solution under Linux, changing win_shell for shell, although I slightly modified the suggestion so it aligns more closely to bash shell in Linux.

Use async and poll for the network restart task.
Then set_fact to update the nodes IP.
Next wait until the ssh port responds on the new IP.
Finally continue on with any remaining tasks.

  - name: Async restart of networking.service 
    shell: "sleep 1; systemctl restart networking.service &"
    args:
      executable: /bin/bash
    async: 100
    poll: 0
    
  - name: set_fact for the nodes new IP
    set_fact:
      ansible_host: "10.0.0.50"

  - name: wait_for ssh port access
    local_action:
      module: wait_for
      host: "{{ ansible_host }}"
      port: 22
      delay: 60
      state: started
    register: network_responding

Then add another task to the playbook after registering the wait_result and that task can have a conditional when clause like:

when: network_responding|bool == true

I converted the restart to shell with bash, backgrounding the restart operation. This may not be needed but YMMV trying to use the same logic with ansible.builtin.service, testing should be pretty simple to compare if doing this without shell is also viable.

+ 1

inframan

3/7/24, 10:10 AM

Hi Trevor, sorry for the delay, went in hospital for many days... This works great ! thanks a lot :) now i just have to handle the SSH host identification & keys but it won't be tough.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: How to handle network changes and restart with Ansible?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.