What were you trying to do that didn't work?

The 'rhel-10.1-x86_64-dvd.iso' and also a Satellite synced repo 'Red Hat Enterprise Linux 10 for x86_64 - BaseOS Kickstart 10.1' contain only "redhat-release-10.1-16.el10.x86_64", not "redhat-release-10.1-17.el10.x86_64" or a later version, which is resulting issue while the kickstart %post doing a standard 'dnf update' as follows:

~~~
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
The GPG keys listed for the "Red Hat Enterprise Linux 10 for x86_64 - AppStream (RPMs)" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: gnupg2-smime-2.4.5-3.el10_1.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: GPG check FAILED

~~~

What is the impact of this issue to you?

• Post "Kickstart" job for updating packages affected

  Please provide the package NVR for which the bug is seen:

• "redhat-release-10.1-16.el10"

  How reproducible is this bug?:

Steps to reproduce

1. Provision a "RHEL 10.1" host
2.  Observe the kickstart %post standard 'dnf update' output that fails with the said error.

Expected results

• The kickstart %post standard 'dnf update' should not throw the error.

  Actual results

• The kickstart %post standard 'dnf update' failed for RHEL 10.1 host