@Glowsome, thanks for the 'ansible-fix',
we're using saltstack (slightly different architecture - client connects to server, not vice versa) that's why we currently workaround using the hook script.
btw. i reported the bug and it seems to be...
I have also been seeing this type of errors.
My running environment:
- HP DL360Gen9 Servers
The Seen errors seems to occur when under CPU the selection is made (or changed) to:
x86-64-v4
However if selecting x86-64-v3
all keeps working.
I...
On my end i have deployed my workaround via Ansible:
- name: Place override for NetworkManager and resolv.conf
ansible.builtin.copy:
content: |
[main]
dns=none
dest: /etc/NetworkManager/conf.d/00-dns.conf
when:
-...
Hi, we face the same issue.
and i can confirm the above mentioned workaround is working.
(we currently apply it via a hook-script - i wonder if this just works by accident?)
to me - the actual issue - looks like to be related to having multiple...