Since multiple packages are facing this issue,an option to fix it is to call a module build with 
$rhpkg module-build --optional rebuild_strategy=all

This will force a rebuild of every package in the module instead of doing a manual bump for each package.

The problem is that the NVR of some packages inside the virt module ended up having a lower NVR when compared to packages in 8.6.

Fixing this requires a module re-build (that Jon already triggered) with absolutely no code change. This is basically risk-free.

If we don't do it: Users will still have the latest code, so this isn´t a regression (even if it looks like one). BUT the NVR of the packages will be mixed up and can generate doubts and questions (this BZ for example). In order to provide the best experience as possible for our users, we want to bump the module-build-id in the package NVR.

Run the module_check.py in https://github.com/yalzhang/module_check/blob/master/check_module.py to compare current module with the latest 8.6.z module, the result is as expected.

# python3 module_check.py   virt:rhel:8060020220901235457  virt:rhel:8070020220921004438
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use subscription-manager to register.

Last metadata expiration check: 3:36:21 ago on Thu 22 Sep 2022 05:26:52 PM EDT.
Package rpmdevtools-8.10-8.el8.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Notes: It is not recommended to compare modules in 2 different streams.
The argv should be in format 'virt:stream:version', like: virt:rhel:8000020190530233731, argv[1] is the released one(older), and argv[2] is the current one(newer)

Compare 2 modules below:
virt:rhel:8060020220901235457 virt:rhel:8070020220921004438
(1) PKG NUM CHECK:
Current pkg num is the same as the released pkg num: 201

(2) PKG NAME CHECK:
Current new added pkg: []
Current deprecated pkg: []
Package name not change in current module compared the release one!

(3)PKG VERSION CHECK:
Run cmd: rpmdev-vercmp $cur_ver $rel_ver one by one to ensure current ver is newer than the released one.
If no waring message, it is fine.

(4)CHECK CURRENT PROFILE:
profile pkg is ['libguestfs\n', 'libvirt-client\n', 'libvirt-daemon-config-network\n', 'libvirt-daemon-kvm\n']
The profile pkg not change.

(5)PROFILE NAME CHECK:
Profile info is Profiles         : common [d]
Default profiles : common

Profile name check OK

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7472