Skip to content

BGP: Restart cifmw-dnsmasq after network configuration #3548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fultonj wants to merge 1 commit into from
Closed

BGP: Restart cifmw-dnsmasq after network configuration #3548

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions playbooks/bgp/prepare-bgp-spines-leaves.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -589,3 +589,23 @@

- name: Apply the BGP default routes
ansible.builtin.include_tasks: tasks/apply_bgp_default_routes.yaml

# Workaround for OSPRH-23100: Restart cifmw-dnsmasq on hypervisor.
# The dnsmasq service sometimes stops responding to DNS queries after
# BGP network configuration, causing EDPM deployment to fail when
# compute nodes cannot resolve package repository hostnames.
- name: Restart cifmw-dnsmasq on hypervisor (OSPRH-23100 workaround)
hosts: hypervisor
become: true
tasks:
- name: Restart cifmw-dnsmasq service
ansible.builtin.systemd:
name: cifmw-dnsmasq
state: restarted

- name: Wait for dnsmasq to be ready
ansible.builtin.wait_for:
port: 53
host: 127.0.0.1
delay: 2
timeout: 30