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.
Bug 1171282 - Applicability Generation does not take into account repository packages, only errata packages
Summary: Applicability Generation does not take into account repository packages, only...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Jason Montleon
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On: 1171280 1178920
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-05 19:42 UTC by Justin Sherrill
Modified: 2017-02-23 20:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1171280
Environment:
Last Closed: 2015-08-12 13:59:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Sherrill 2014-12-05 19:42:32 UTC 
+++ This bug was initially created as a clone of Bug #1171280 +++

Description of problem:

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1171278

But if an errata is in multiple repositories, applicability generation calculates whether the errata is applicable based on all the packages in the errata, not based on whether the packages are actually in the repository that the system is bound to.


Version-Release number of selected component (if applicable):
2.4.1

How reproducible:
Always

Steps to Reproduce:
1. Sync RHEL 5
2. Sync RHEL 6
3. Bind a rhel 5 and a rhel 6 system to their respective repos
4. Generate, fetch, and note applicability
5. Update both systems fully
6. Generate, fetch and note applicability again

Actual results:
On either step 4 or 6, the appliability will be wrong.  You may see errata not show up that should show up, or you may see errata show up as applicable when they are not.


Additional info:
The description is a bit vague, because it is complicated by https://bugzilla.redhat.com/show_bug.cgi?id=1171278

The solution to that bz may solve this issue by itself, or it may not.
Comment 1 RHEL Program Management 2014-12-05 19:46:22 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 4 Tazim Kolhar 2015-05-08 08:46:06 UTC 
VERIFIED :
# rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.11-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-debug-1.7.2.19-1.el7sat.noarch
foreman-compute-1.7.2.19-1.el7sat.noarch
foreman-vmware-1.7.2.19-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-libvirt-1.7.2.19-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.19-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch

steps:
1. Sync RHEL 5
2. Sync RHEL 6
3. Bind a rhel 5 and a rhel 6 system to their respective repos
4. Generate, fetch, and note applicability
5. Update both systems fully
6. Generate, fetch and note applicability again
only applicable errata is shown in the list
Comment 5 Bryan Kearney 2015-08-11 13:24:39 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 6 Bryan Kearney 2015-08-12 13:59:25 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.