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.

Bug 2227056

Summary: Rollback of a library (libtpms-0.9.1) in two consecutive errata
Product: Red Hat Enterprise Linux 8 Reporter: Paulo Andrade <pandrade>
Component: libtpmsAssignee: Marc-Andre Lureau <marcandre.lureau>
Status: CLOSED NOTABUG QA Contact: Qinghua Cheng <qcheng>
Severity: low Docs Contact:
Priority: medium    
Version: 8.8CC: coli, ddepaula, jinzhao, jmaloy, juzhang, kkiwi, marcandre.lureau, mrezanin, qcheng, sct, vharyan, yfu
Target Milestone: rcKeywords: Reopened
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-20 12:44:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paulo Andrade 2023-07-27 15:47:50 UTC
Can you explain to why errata RHSA-2023:3822 (2023-06-27) requests the installation of library libtpms-0.9.1-2.20211126git1ff6fe1f43.module+el8.8.0+18453+1482ba89.rpm (compiled on 2023-03-23) and errata RHSA-2023:2757 (2023-05-16) requests the installation of library libtpms-0.9.1-2.20211126git1ff6fe1f43.module+el8.8.0+18453+ e0bf0d1d.rpm (compiled on 2023-03-27)?

The latest errata rollback correction done by previous errata without building new library. Do you confirm my understanding? And this is the aim of this correction?

dnf installs the library libtpms-0.9.1-2.20211126git1ff6fe1f43.module+el8.8.0+18453+1482ba89.rpm by updating library libtpms-0.9.1-2.20211126git1ff6fe1f43.module+el8.8.0+18453+ e0bf0d1d.rpm

Comment 1 Marc-Andre Lureau 2023-07-28 13:11:05 UTC
I guess RHSA-2023:3822 should pick the last build instead. I can't manage to find/open the 3822 errata...

Comment 2 John Ferlan 2023-07-31 12:25:25 UTC
Jon - can you take a look and help out here with the errata and module build.

Comment 3 Miroslav Rezanina 2023-07-31 13:48:29 UTC
Not sure what happened here, should be answered probably by someone responsible for module build infrastructure.

However, looking on NVR shows that both build have same content (libtpms-0.9.1-2) and errata shows that 3822 use newer module build than 2757. Whatever reason is for using older build this should has no impact on usability.

Comment 15 John Ferlan 2023-09-20 12:44:17 UTC
Following through on Danilo's advice to close notabug. There's a lot of data in private comments - since the poster is a Red Hat employee they should be able to read.

Long story short is the differences appear to be a result of timing of module builds related to the timing of y & z stream release creation.

There is no content difference just quirks of the module build system which will no longer be used by the Virt Team.