I’ve got the same issue, with 2 out of 9 server having no issues and already updated to 1.8.10-11.
The actual reason for this seems to be an inconsistent mirror update for the epel repository, with some mirrors still having iptables-services.noarch 1.8.10-4.1.el9, which blocks the update of the baseos packages.
You can wait for the epel mirror sync to finish.
This works for me: force dnf to pick another epel mirror. I did this by simply adding “&country=de” to the metalink in the repository definition /etc/yum.repos.d/epel.repo:
[epel]
…
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-9&arch=$basearch&infra=$infra&content=$contentdir&country=de
That’s no guarantee the new mirror is up to date though, in case that doesn’t work you’ll need to pick a mirror yourself.