search

viccross / ansible-playbooks

My collection of Ansible playbooks for various tasks (dominated by Openshift, currently)
Apache License 2.0
2 stars 3 forks source link

`ipconf.sh`: lack of DNS can impact Ansible playbooks #190

Closed viccross closed 8 months ago

viccross commented 8 months ago

Clearly it doesn't always happen... I did a restore in my zPDT and found that the Ansible playbook to reconfigure DNS did not run -- it was stuck on "gathering facts". Prior to running the playbook I do a shutdown of named-chroot, and since it is the only effective nameserver in /etc/resolv.conf we have a problem. Why does it not always happen, though?

viccross commented 8 months ago

Missed explaining why this is a DNS thing: apparently the "gather facts" task does things like dnsdomainname and hostname in the background. So depending on the name resolution fallback (this is the part that doesn't make sense to me) these can hang seemingly indefinitely (seemingly because, as already mentioned, it doesn't always happen... maybe it was just because it's zPDT...).

viccross commented 8 months ago

So how to fix... one way would be to move the stop and start of named-chroot into the playbook so that tasks like "gather facts" are not impacted. Also, replacing /etc/resolv.conf with full details of the local network (rather than doing item-by-item replacements in the existing file) would provide greater reliability when named-chroot is down for any reason (and removing the "Generated by NetworkManager" tags will also be useful, since it isn't).