I think it might be the SELinux. so check and see if you have any unlabeled permissions. I would also check getenforce if it is enforcing it; it is going to be SELinux
Edit,
from what i can find its a common thing i would try to do
sudo touch /.autorelabel
sudo reboot
# then rerun your cat again and see if you have permissions.
you could also try
sudo setenforce 0
sudo cat /var/log/dnf.log
I would just not leave the setenforce at 0.
also what are you running this in? as in what environment (KVM, proxmox, vmware)?
Yes, it would be the staff_t/_u/_r. I don’t know if you are going to keep running on staff_u but it does not do an auto transition for sudo commands, as it is a cloud user account, and I believe it is for security reasons.
you could do
sudo semanage login -m -s unconfined_u #username
this would get you what you’re looking for as a sudo command account
I believe it’s because it’s a cloud distro so they know people setting it up are going to forget and not think to lock down the system so they pre lock it so you can’t mess it up which I honestly think is a good thing so there is less of a chance that a fresh install gets permission hopping hackers