Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionyalzhang@redhat.com
2022-09-15 11:23:52 UTC
Description of problem:
Some packages in rhel 8.7 virt:rhel module are older than the ones in rhel 8.6.z
Version-Release number of selected component (if applicable):
virt:rhel:8070020220826181159
How reproducible:
100%
Steps to Reproduce:
1. Some packages in this rhel 8.7 virt:rhel module are older than the ones in virt:rhel:8060020220829210852 which is the latest rhel 8.6.z virt module;
The packages includes:
libiscsi
nbdkit
netcf
libvirt-dbus
hivex
libnbd
perl-Sys-Virt
2. Compare by rpmdev-vercmp:
# yum module info virt:rhel:8070020220826181159 | grep libiscsi-0.*x86_64
: libiscsi-0:1.18.0-8.module+el8.6.0+12861+13975d62.x86_64
# yum module info virt:rhel:8060020220829210852 | grep libiscsi-0.*x86_64
: libiscsi-0:1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64
# rpmdev-vercmp libiscsi-1.18.0-8.module+el8.6.0+12861+13975d62.x86_64 libiscsi-1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64
......
libiscsi-1.18.0-8.module+el8.6.0+12861+13975d62.x86_64 < libiscsi-1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64
Actual results:
The package in rhel 8.7 virt module is older than the ones in rhel 8.6.z
Expected results:
rhel 8.7 should be newer than rhel 8.6.z
Additional info:
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.
Comment 10yalzhang@redhat.com
2022-09-23 01:05:57 UTC
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
Description of problem: Some packages in rhel 8.7 virt:rhel module are older than the ones in rhel 8.6.z Version-Release number of selected component (if applicable): virt:rhel:8070020220826181159 How reproducible: 100% Steps to Reproduce: 1. Some packages in this rhel 8.7 virt:rhel module are older than the ones in virt:rhel:8060020220829210852 which is the latest rhel 8.6.z virt module; The packages includes: libiscsi nbdkit netcf libvirt-dbus hivex libnbd perl-Sys-Virt 2. Compare by rpmdev-vercmp: # yum module info virt:rhel:8070020220826181159 | grep libiscsi-0.*x86_64 : libiscsi-0:1.18.0-8.module+el8.6.0+12861+13975d62.x86_64 # yum module info virt:rhel:8060020220829210852 | grep libiscsi-0.*x86_64 : libiscsi-0:1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64 # rpmdev-vercmp libiscsi-1.18.0-8.module+el8.6.0+12861+13975d62.x86_64 libiscsi-1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64 ...... libiscsi-1.18.0-8.module+el8.6.0+12861+13975d62.x86_64 < libiscsi-1.18.0-8.module+el8.6.0+14480+c0a3aa0f.x86_64 Actual results: The package in rhel 8.7 virt module is older than the ones in rhel 8.6.z Expected results: rhel 8.7 should be newer than rhel 8.6.z Additional info: