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.
HP would like to see exact version numbers for the components in RHEV-H, so that they can see how much of testing they can leverage from RHEL (identical components, versus kernel has changed slightly with 2 additional patches in kernel, 2 additional patches in libvirt in RHEV-H 6.x GA than in RHEL 6.x GA in those components). Including the manifest file in the ISO would provide exact data to our partners.
Putting the manifest(s) in the rpm directly is not an easy fix, at least in an automated, repeatable way. It might be doable with libguestfs, but that would take investigation. The easiest way to achieve something like this would be to extract the manifests during rpm %post processing, but that's not ideal if someone extracts the rpm manually using rpm2cpio.
Can we see if HP is ok with the manifest in the ISO only? I'd really rather not make this change unless it's a showstopper for HP.
As for knowing package differences between 6.x RHEL GA and 6.x RHEV-H GA, we ship *exactly* the same packages for kernel, libvirt, etc.
BethZ to update HP regarding RHEV-H manifest provided in the ISO. We would rather not add this manifest in RPM. Let's close this bug after gathering HP feedback.
Comment 8RHEL Program Management
2012-07-10 08:23:12 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 9RHEL Program Management
2012-07-11 01:47:42 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.