CHG: CentOS bug #16988 hotfix, systemd-resolved fails to start on boot (common/update-config)

parent 0a3ad26b
# Migration play
# vim:et ts=2 sw=2 sts=2 syntax=yaml filetype=yaml
# - CentOS bug #16988
---
- block:
- name: Update systemd-resolved
include_role: name=common/update-config
when: ansible_distribution_major_version == '8'
tags: ['up']
......@@ -8,9 +8,24 @@
register: s
- set_fact: update_resolv="{{ '=inactive' in s.stdout }}"
when: canonical_resolv == 'auto'
- name: Start systemd-resolved
systemd: name=systemd-resolved state=started enabled=yes
- block:
# via CentOS #16988, witnessed on C8.2019, fixed in systemd 239-40
# https://bugs.centos.org/view.php?id=16988
- name: Apply ProtectSystem= usage
include_role: name=systemd/override-config
vars:
service: systemd-resolved
config:
- group: Service
vars:
ProtectSystem: "strict"
PrivateTmp: "yes"
when: ansible_distribution_major_version == '8'
- name: Start systemd-resolved
systemd: name=systemd-resolved state=started enabled=yes
when: not update_resolv
# Witnessed on fastpipe.io, falling back to dns using advertised
# nameservers times out on FQDN lookup that impacts hostname -f
# blocking normal startup of ApisCP
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment