Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
the official virt-who package is built today(2017-03-29): virt-who-0.19-2.el7
but the SatTools virt-who package(virt-who-0.19-2.el7sat) has been built on 2017-03-15
official virt-who (virt-who-0.19-2.el7) includes many bugfix, but SatTools virt-who package(virt-who-0.19-2.el7sat) didn't include these bugfix,
In my opinion, SatTools virt-who package should keep to sync with the official version,
if a official virt-who-0.19-2.el7 is created, please don't create virt-who-0.19-3.el7sat for SatTools, virt-who-0.19-2.el7sat or virt-who-0.19-2.1.el7sat will be more better.
There is a customer scenario:
the customer install virt-who-0.19-1.el7 from the RHEL repository, but one day he found there are two new packages for update:
1). virt-who-0.19-2.el7 (from RHEL) => build based on upstream, includes all the bugfix
2). virt-who-0.19-2.el7sat (from SatTools) => re-build based on virt-who-0.19-1.el7, no more bugfix,
The customer will think virt-who-0.19-2.el7 and virt-who-0.19-2.el7sat are the same version, but in fact not the same version, if update to virt-who-0.19-2.el7sat, he will miss some critical bugfix patch.
Given all of the various changes that have happened in virt-who releases, this is no longer an issue, and should not be an issue for pending EL7 or Sat releases. Please reopen if we find otherwise.
Comment 7Shane Ellerthorpe
2017-05-24 12:27:18 UTC
I just found this exact issue injected into my system today. I am still using the Redhat 6, however the working virt-who-0.18-3.el6 was definitely upgraded to a broken virt-who-0.19-2.el6sat version.
I am working again after downgrading the version. I agree that having this present in 2 different channels will still be an issue. If a newer version is coming out, I haven't seen it yet. The Redhat server rpms channel still only shows 0.18.3 as the latest.
I'm wondering if I should just filter this package out from the Satellite channel completely to prevent the bad package install from taking place again.