@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...
In essence neither RHEL, nor Rocky recommend (or suggest/support) upgrading in this way, so if Alma follows the same scheme then yeah.
Unsupported, but if it works .. it counts ;)
The link i used , and validated the migration with ( explicitly for RockyLinux) was Upgrade Rocky Linux from 9.6 to 10
In the comments under this article also the issue described as to how to solve the /etc/resolv.conf not correctly populated...
i updated a Rocky9 LXC to 10 without issues ( taking into account an issue i have resolved after upgrade where when using dns-settings in PM to 'use host')
-> this is documented somewhere a bit down.
- Glowsome
Hi all,
I might have overlooked if this was posted before, but just wanted to share.
But when deploying a new LXC with the rocky10 (20251001) -template, the following is experienced when setting it to use host dns domain and server:
-...
I found the issue, earlier this year we rolled out an SSH hardening that set AllowTcpForwarding to no. Now that I changed this value to yes the migration works again.
thanks all for helping!