On 15/06/2021 15:41, Ed Greshko wrote:
If I were you I may consider checking the upgrade logs.
While not using the chroot service I just upgraded my internal bind system from F33 to F34.
I do have all of these installed on the upgraded system.
I had another F33 VM which needed upgrading. Before the upgrade I established a named-chroot
environment.
I performed the upgrade.
Upon reboot named-chroot was still enabled and it started just fine. No problems noted.
FWIW, I would also check to make sure that the inodes /etc/named.root.key is the same as
/var/named/chroot/etc/named.root.key
[root@f33g etc]# ll -i /var/named/chroot/etc/named.root.key /etc/named.root.key
486885 -rw-r--r--. 1 root named 686 Jun 3 22:47 /etc/named.root.key
486885 -rw-r--r--. 1 root named 686 Jun 3 22:47 /var/named/chroot/etc/named.root.key
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
